Select Language:
If you’re experiencing a problem where emails sent internally between WorkMail users appear in your Sent Items but aren’t received by the intended recipient, don’t worry—there are a few simple steps you can follow to fix this.
First, check your domain’s MX records to make sure everything is set up correctly. Your WorkMail should be the only entry listed, and it should have the lowest priority. Having multiple MX records can cause emails to be routed improperly, leading to delivery issues.
Next, review your DMARC settings within the Amazon WorkMail console. Incorrect configurations here can interfere with email delivery. Proper DMARC settings help ensure your emails are accepted and properly routed.
Then, take a look at your Amazon SES inbound rules. If these rules include actions other than working directly with WorkMail, they might be causing failures that prevent internal emails from being delivered properly. Make sure the inbound rules are correctly set up to support your email flow.
It’s also important to verify that Amazon WorkMail has the correct permissions to use your domain. You can do this by re-adding your domain in the WorkMail console. This process prompts the system to check your domain settings and fix any issues.
Since you’ve already enabled message tracking in CloudWatch but only see messages marked as “sent,” it’s a good idea to check your SES permissions. Sometimes, permission issues can cause emails to be sent but never actually arrive in recipients’ inboxes.
For outbound email problems, confirm that your SPF record includes Amazon SES. You can verify this by reviewing your domain’s DNS settings in the WorkMail console; this helps prevent your emails from being marked as spam or rejected.
If these steps don’t resolve the problem, you may need to create a custom policy in Amazon SES that explicitly authorizes WorkMail to send emails on your behalf. This helps ensure everything is properly authorized for smooth email delivery.
Following these steps should help you solve most internal email delivery issues. If you still experience trouble, consider reaching out to Amazon support or consulting more detailed guides on email routing and permissions.




