Emails not being delivered

[thedjsessions]

Hello,

I am sending out emails to previous recipients that I have sent to several times in the past and personally know them and I am getting the emails rejected with teh following message for several of them –

An error occurred while trying to deliver the mail to the following recipients:
a**************@gmail.comReporting-MTA: dns; a27-31.smtp-out.us-west-2.amazonses.com

Action: failed
Final-Recipient: rfc822; a************@gmail.com
Diagnostic-Code: smtp; 550-5.7.26 Unauthenticated email from thedjsessions.com is not accepted due to
550-5.7.26 domain’s DMARC policy. Please contact the administrator of
550-5.7.26 thedjsessions.com domain if this was a legitimate mail. To learn
550-5.7.26 about the DMARC initiative, go to
550 5.7.26 https://support.google.com/mail/?p=DmarcRejection 41be03b00d2f7-b2c38087325si2517054a12.663 – gsmtp
Status: 5.7.26

Why is this happening and how do I fix it?

These are not spam emails and I have multiple email interactions with every email I am sending using your plugin for years.

Please advise.

[thedjsessions]

I am also getting this message in WordPress when I click on the Amazon SES plugin –

“There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.”

I am not receiving any emails there.

I am also seeing this on my Plugins page in WP under the Amazon SES plugin –

Update failed: Download failed. Payment Required

My Amazon SES account is up to date with payments and I was sending emails with your plugin from Feb 2024 to August 2024 with no issues. I did see that my license did expire in May of 2023 but I was still able to send in late 2023 and in 2024.

Can someone help me to resolve this?

[Michael]

Hello,

there are two different issues going on here. The first one, for which you’re getting the refusal message from Amazon SES, is that you didn’t set up DMARC record on your server. Please proceed to do so by contacting your hosting provider.

The other issue is caused by the fact that you can’t download updates to premium addons without a valid license. The addons will continue working without updates, but in the long run you may be missing critical updates and we do not guarantee them to work forever.

Michael

[thedjsessions]

I do have the following DMARC’s setup and I had never changed them in the past and it was working fine.

AMAZON SES DMARC – txt _dmarc “v=DMARC1; p=none;” 1 Hour

Godaddy DMARC – txt _dmarc v=DMARC1; p=reject; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net; 1 Hour

If I get the $69 a year option will I be able to download the update?

If this doesn’t solve the issue can I get a refund?

[thedjsessions]

Oh one other note…

I did update the records last night and GoDaddy said it could take up to 48 hours to propagate.

I will be doing some testing today.

I am using Amazon SES version 1.4.2 and I see there is a newer version 1.5.7.

Were there significant changes that would stop that version from working?

Would a STMP option be a work around Amazon SES?

[thedjsessions]

I was able to send a test email from the System>Delivery Tab and it came through quickly.

I did do a test email for two different newsletters and it sent it out and was received.

Would that be using Amazon SES to do that test send?

[thedjsessions]

I just got this email from Amazon SES –

[Starting September 15, 2025, emails about AWS Health events will be delivered via the AWS User Notifications service. You can opt-in to this enhanced experience today. See footer for details.]

Congratulations! Amazon SES has successfully detected the MX record required to use darran.thedjsessions.com as a custom MAIL FROM domain for verified identity thedjsessions.com in AWS region US East (N. Virginia).

You can now use this MAIL FROM domain with thedjsessions.com and any other verified identity that is configured to use it. For information about how to configure a verified identity to use a custom MAIL FROM domain, see http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from-set.html .

Please note that this email only applies to AWS region US East (N. Virginia).

Thank you for using Amazon SES.

[Beginning September 15, 2025, emails about AWS Health events will be delivered via AWS User Notifications. AWS User Notifications provides de-duplication of emails within AWS organizations and a configuration interface to manage subscriptions. Emails about AWS Health events will be sent from a new sender address: health@aws.com and in HTML format, rather than plain text. Recipients may need to validate that email rules continue to work with the changes. To switch to the new experience early, please visit https://console.aws.amazon.com/notifications/home?region=us-east-1#/managed-notifications%5D

So my emails should be able to go out now correct?

[Michael]

Hello,

as I said, there are two different issues going on here.

1. That Dmarc message is probably caused by missing Spf and Dkim records or wrongly set. Please check this with your hosting provider.

2. To debug that php fatal error appearing when you click on Amazon SES addon, we need to take a look at the php logs. You can either activate WordPress debug mode / logging or look for php logs on your server. Let us have them, so we can verify whether that issue is caused by the old Ses addon or by something else (e.g. a conflict etc..)

[Author]

Posts