Can send but not receive email from AWS workmail.

0

Hi,

I can send mail fine from workmail but I am unable to receive anything. When I try sending email to the account I created under my domain admin@hallbrawl.com I recieve a response from mailer-daemon: "This message could not be delivered due to a recipient error. Please try again later.". All the records the domain verification in work mail are added to route 53 and verified. I purchased the domain through route 53.

plawler
質問済み 3年前2859ビュー
5回答
1

I was having an issue receiving and was using Thunderbird client but I didn't have an Inbound Rule set up for mine. I went to: Amazon SES > Configuration: Email receiving and opened my INBOUND_MAIL entry...

  • I duplicated a rule that was there that was working for another domain address I had and changed the unique rule id and ...
  • changed the organization "arn" identifier (in two places, I had an entry for WorkMail too) and...
  • enabled TLS and changed the name of Recipient condition (and deleted the aws auto-created one)

It took me through the wizard tool basically, and that worked for me.

回答済み 5ヶ月前
0

Hi,

I'm sorry to hear you're having problems receiving mail. I took a look at your account and everything seems to be in order. I do see that the Inbound rule that is configured in SES has been altered to just your email address instead of your domain. This means that just your user can receive mail and that your awsapps.com domain will not work.

I recommend that you add your domain again in the WorkMail console (no need to delete it first) to set the inbound rule to the correct details.

Kind regards,
Robin

AWS
エキスパート
回答済み 3年前
0

I readded the domain, and removed the ses rule to just the one email address and it can receive email now, thank you!

plawler
回答済み 3年前
0

I ran into this same thing. Strangely, it was working yesterday, then started failing today. I happen to be sending automated outbound emails via SES, but using WorkMail to receive and manually respond to inbound emails on the same domain. So, for me, I think the issue was using the same domain in SES and WorkMail. To resolve it, I had to create an inbound rule in SES (same as one of the responses above) and then create an Action type "Integrate with Amazon WorkMail" using the organization ARN and all of that, same as the above response.

The WorkMail domains page (e.g. Amazon WorkMail > Organizations > [org name] > Domains > [domain name]) has a feature where it double-checks or creates all DNS entries for you. It seems like it could pretty easily detect if some of these DNS entries were set up with SES and add an info/warning box here that an inbound rule will be needed.

wheaney
回答済み 7日前
-1

shut this WorkMail down, it is a trouble for small businesses. selling something not functional properly.

回答済み 1年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ