Webinoly is just the perfect tool for NGINX experts. Give it a try!
0 votes
by Talented

This is a new problem. I have Postfix working fine -- I can send email from the mail command in the shell and php mail as well and I receive it just fine.

However, if WordPress sends an email, Postfix can't send, because AWS SES (Amazon SMTP) rejects it with 554 Transaction failed: Duplicate header 'MIME-Version'. I've tried using the "check email" plugin to force send emails from WordPress. Details from the mail log:

Jan 23 08:13:04 webg1 postfix/smtp[61718]: E494C7FAC2: to=<myemail@gmail.com>, relay=email-smtp.us-west-2.amazonaws.com[]:587, delay=1, delays=0.02/0.02/0.67/0.31, dsn=5.0.0, status=bounced (host email-smtp.us-west-2.amazonaws.com[] said: 554 Transaction failed: Duplicate header 'MIME-Version'. (in reply to end of DATA command))

I've learned that AWS SES rejects multiple mime header lines, and it appears WordPress is adding it twice somehow. I also now realize that none of my sites are able to send email (I hadn't noticed it yet).


1 Answer

0 votes
by Expert

I will just say one thing:

  • We use AWS SES in this site and for all my other WP and simple sites and email works just fine.

I'm pretty sure you are having issues with your own configuration. Please, check very carefuly what you are doing.


by Talented
I haven't done any non-standard configuration that I know of. I switched this server to Mailgun to see if it would help, and it worked -- emails are sending fine from WordPress with Mailgun, but they are showing up as spam now. I would like to go back to SES but am not sure how to avoid having two MIME headers inserted.
by Expert
So, I can assume you are using a WP Plugin for the SMTP integration, maybe you should ask to the plugin author about this issue, I have no idea what they are doing.

What I can recommend is using SES at server level, check this tutorial:

by Talented
I am already using SES at the server level (no wp plugin for smtp). I forgot to mention that. Also, I forgot to mention that this setup does work for me on my Hetzner server, just not on the Google server. I configured them both almost the same way. It would be hard to figure out what is different.

The reason I think this is so strange is that it's only SES that doesn't work -- when I switched to Mailgun it worked great. The error from SES refers to duplicate MIME headers, and I found some information from other people suffering from the same issue -- some recommend a change in wordpress core is needed:


I'm probably ok for now since Mailgun works, although I would rather be using my SES setup.
by Expert
That's weird!

I can confirm I'm using SES with WordPress and I have no problems, I just followed the tutorial I mentioned before.
by Talented
Yeah, it's weird for sure. I hope someone knows and comments!
Welcome to the Community site for Webinoly.

Our Optimized LEMP Web Server is a powerful set of commands for doing just about anything you could wish.

With Webinoly you can set up your NGINX web server in just one step.

* * * * * * *

To report a bug, please create a new issue on GitHub or ask a question here with the bug tag.
Webinoly Support Paypal Donations

PayPal · GitHub Sponsors · Bitcoin

It is very important that any visitor to the site read the disclaimer, terms of use and privacy and legal statement before start browsing.