1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
This indicate that there's an inbound mail routing issue. use the following steps below to identify and fix the issue:
- Check the MX record for the domain associated with your Amazon WorkMail organization. WorkMail should be the only entry and should have the lowest priority. Multiple MX records can lead to the wrong service receiving messages. For more information about MX records, see Verifying domains.
- Check the Domain-based Message Authentication, Reporting, and Conformance (DMARC) settings for your organization in the Amazon WorkMail console. DMARC records are used to protect against common attacks, such as spoofing or phishing, that can compromise a user's account credentials. For more information about DMARC, see Enforcing DMARC policies on incoming email.
- Check the Amazon Simple Email Service inbound rule. If the rule contains actions other than Amazon WorkMail, those actions can fail and cause Amazon WorkMail to stop receiving mail. For more information about Amazon SES rules, see Integrate with Amazon WorkMail action in the Amazon Simple Email Service Developer Guide.
- Enable message tracking in Amazon WorkMail, and then check the logs for delivery problems. For more information about message tracking, see Enabling event logging.
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 5달 전
- AWS 공식업데이트됨 2년 전
Thanks for the answer. Now I see, I need to add "10 inbound-smtp.us-east-1.amazonaws.com" MX record. But my "namecheap" dns provider does not accept such value. How to proceed here?