We typically install the Post SMTP WordPress plugin on client sites to improve email deliverability. But, sometimes, it will send you a cryptic—and frequently misspelled—warning that it couldn't send one of the messages to you.
These errors only happen after the plugin is set up and configured correctly. If you're having trouble with the initial settings, please review this article instead: [coming soon]
Invalid "To" E-mail Address
This is the most common Post SMTP email error. In this scenario, the person (or bot) who completed your contact form or purchased something from your store typed their email address wrong.
Common Email Address Mistakes:
- Typo in domain name: They typed ".con" instead of ".com"
- Period or invalid character before the @ symbol: This typically happens when a bot completes your contact form with a Gmail address like abc.123.xyz.@gmail.com. The period after "XYZ" is invalid, so WordPress can't send the message, and Post SMTP sends you a warning so you can fix the problem.
Error Message
Here is the full text of the error message with the domain name changed:
Subject: https://www.your-domain.com: Post SMTP email error
You getting this message because an error detected while delivered your
email.
For the domain: https://www.your-domain.com The log to paste when you
open a support issue:
Invalid "To" e-mail address "username@icloud.con"
How To Fix Post SMTP 'Invalid To E-mail Address' Notification
In some cases, a legitimate customer will unintentionally cause this problem. You can fix it by editing their email address and trying again. It's obvious when they mistype common email provider domain names like Gmail.com, Yahoo.com, AOL.com, and iCloud.com.
If a fake bot email account caused the error, ignore it and delete the notification.
413 Request Entity Too Large
This might happen if your contact form allows lots of text or characters or if there's a very large attachment. However, we typically see this when the Solid Security Pro plugin sends a massive email with several thousand file change notifications in the body.
Solid Security Pro has a feature called File Change Detection that sends you a daily summary email with a list of every file that has changed since the last check. Sometimes, the previous check fails, so when Solid Security Pro runs the next time, it lists every single file on your website because the plugin thinks everything has changed.
Read more about SolidWP's file change detection and notification feature: https://help.solidwp.com/hc/en-us/articles/202797940-Solid-Security-File-Change-Detection
Here are our recommended SolidWP File Change exclusions:
Error Message
Here is the full text of the error message with the domain name changed:
Subject: https://www.you-domain.com: Post SMTP email error
Body: You getting this message because an error detected while delivered your email.
For the domain: https://www.your-domain.com
The log to paste when you open a support issue:
Code: 413, Message: Request Entity Too Large, Body: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>
How To Fix Post SMTP '413 Request Entity Too Large' Notification
This error message is rare and typically occurs on large WordPress sites with many themes, plugins, and uploads.
- Troubleshoot Solid Security Pro: The SolidWP File Change Detection job failed the previous day and was likely caused by a missed or failed cron job.
- Disable File Change notifications (not detection): The File Change Detection feature should remain enabled to track changes to your website files. But you don't need the daily notifications, especially if you're experiencing intermittent cron job issues, so turn them off here: Security > Notifications > File Change.
We've noticed this happens more often when clients install the unnecessary WP Crontrol plugin. Our servers take over the WordPress cron functions to reduce the website's workload, so we do not recommend using WP Crontrol.
Contact Support
If your error isn't listed here, please contact support.
Comments
0 comments
Please sign in to leave a comment.