Hi Marc > https://mxtoolbox.com/SuperTool.aspx?action=mx%3aleunet.ch&run=toolpage > > Suggest you fix that and come back to them.
DMARC? It's not an error, it's not a requirement. The AWS customer who notified the problem uses this email domain: https://mxtoolbox.com/SuperTool.aspx?action=mx%3aedudip.com&run=toolpage Also has not DMARC entry. Or look at a well know big email service operator: GMX: https://mxtoolbox.com/SuperTool.aspx?action=mx%3agmx.net&run=toolpage Also has not DMARC entry. And Edudip confirmed, they can send email from Amazon SES to GMX recipients. So this was ruled out to be the cause. > In addition, I would have your client add you or a member of your team as a > user in their AWS acct with the ability to add support issues on their acct. Edudip.com is not our client. Our client is under the domain leunet.ch and unable to receive emails sent via Amazon SES. Edudip.com is not related to us. It was just a Amazon SES user who was friendly enough to open a case for the Issue with Amazon SES and got the reply, that we have to fix the issue with the MX or get in contact ourself with Amazon SES to solve the issue. The second part is where we fail because of that stupid amazon policy that you need an AWS account to obtain any kind of support. My attempt to open a 'user' account on Amazon (the one you can order stuff) also didn't help much further as this account also has no way to open an AWS case or access the existing case the Amazon SES customer opened. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
