Problem recieving emails when using AWS SES

[Kinzi]

Hey!

I 've set up sending via SES for a domain (sending works well)

However, I now have a problem receiving email:

550 Mailbox does not exist!

Final-Recipient: rfc822; my@email.com
Action: failed
Status: 4.4.2
Remote-MTA: dns; feedback-smtp.eu-west-1.amazonses.com. (IP.IP.IP.IP, the
server for the domain email.com.)
Diagnostic-Code: smtp; 550 Mailbox does not exist!

Pretty sure this used to work and stopped working after setting up DMARC/DKIM?!?

No idea where to start debugging though - any idea?

[Kinzi]

OH OK so I had an MX record with the SES address in addition to the cloudron one: feedback-smtp.eu-west-1.amazonses.com

Deleted it and it's working again.

Do I not need this for the DMARC/DKIM of SES to work though?

[joseph]

@Kinzi said in Problem recieving emails when using AWS SES:

OH OK so I had an MX record with the SES address in addition to the cloudron one: feedback-smtp.eu-west-1.amazonses.com
Deleted it and it's working again.

Right, you should not put the MX record of SES, only Cloudron. Otherwise, some emails will be delivered to SES and some to Cloudron.

Do I not need this for the DMARC/DKIM of SES to work though?

Yes, it's better to set up those records. Worst case, SES removes the DKIM header generated by Cloudron.

[Kinzi]

@joseph Sorry but this was confusing for me.

So I understand that the mx should be removed. (done)
The questions was: I thought I need that MX for the DMAR/DKIM to work?

I did setup that ses MX following the DKIM/DMARC dokumentation....

[joseph]

@Kinzi said in Problem recieving emails when using AWS SES:

The questions was: I thought I need that MX for the DMAR/DKIM to work?

No MX is not needed for DMARC or DKIM. They are separate concepts.