Here are the troubleshooting steps if your email action configured with the default email id is not getting delivered to the intended users
First, check the logs screen in ARN and see the status of your ARN email rule.
If the rule execution status in logs is ‘Failure’ click on the status to see the exact reason for the failure.
If the rule execution status in logs is ‘Success’, then it means the app did send out the email.
Now if the email isn't received, the problem could lie with the email receiver's service provider. Most likely, the email receiver server is blocking that email. The simple way to verify this is to include a personal email address in the list and then execute the ARN rule. If the personal email address receives the email, then that means the app is generating emails properly.
So next you can check with the email administrator and ensure that emails from ARN’s default email id (autoreleanotes@amoeboids.com or updates@releasenotes.co ) are not blocked.
Recommended
More than often, your users/customers are always likely to receive emails sent from your domain rather than the domain used by our default email id (i.e. amoeboids.com or releasenotes.co)
Therefore, we would recommend you set up your own email id as a sender email id for your ARN email rule actions.
This is very easy to set up via SMTP settings.
Refer to this help guide
