Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

SMTP Errors and Troubleshooting

Response codes

response-codes page anchor

Each SMTP call you make returns a response. 200 responses are usually success responses, and 400 responses are usually deferrals. SendGrid continues to retry resending 400 messages for up to 72 hours. 500 responses are hard failures that are not retried by our servers. This table has possible response codes with example errors and a general explanation of that sort of response.

250Queued mail for deliveryYour mail has been successfully queued! This response indicates that the recipient server has accepted the message.
403You are not authorized to send from that email addressThis means the "from" address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. To learn how to resolve this error, see our Sender Identity requirements.
421Message from (X.X.X.X) temporarily deferredMessages are temporarily deferred because of recipient server policy - often it's because of too many messages or connections in too short of a timeframe. We continue to retry deferred messages for up to 72 hours. Consider temporarily sending less messages to a domain that is returning this code because this could further delay your messages currently being tried.
450too frequent connects from, please try again later.The message failed because the recipient's mailbox was unavailable, perhaps because it was locked or was not routable at the time. We continue to retry messages for up to 72 hours. Consider temporarily sending less messages to a domain that is returning this code because this could further delay your messages currently being tried.
451Temporary local problem - please try laterThe message simply failed, usually due to a far-end server error. We continue to retry messages for up to 72 hours.
451Authentication failed: Maximum credits exceededThere is a credit limit of emails per day enforced in error. Contact support(link takes you to an external page) to remove that limit.
452Too many recipients received this hour (throttled)The message has been deferred due to insufficient system storage. We continue to retry messages for up to 72 hours.
550Requested action not taken: mailbox unavailableThe user's mailbox was unavailable. Usually because it could not be found, or because of incoming policy reasons. Remove these address from your list - it is likely a fake, or it was mistyped.
550You are temporarily blocked from sending emails due to repeated bad requests.Too many bad requests, such as bad sender or bad recipient address, have been sent in a short time frame. A temporary block of a few minutes has been activated to prevent more bad requests until a fix can be implemented.
551User does not exist.The intended mailbox does not exist on this recipient server. Remove these addresses from your list.
552This message is larger than the current system limit or the recipient's mailbox is full. Create a shorter message body or remove attachments and try sending it again.The recipients mailbox has exceeded its storage limits. We don't resend messages with this error code because this is usually a sign this is an abandoned email.
553Invalid/inactive user.The message was refused because the mailbox name is either malformed or does not exist. Remove these addresses from your list.
554ERROR: Mail refusedThis is a default response that can be caused by a lot of issues. There is often a human readable portion of this error that gives more detailed information, but if not, remove these addresses from your list.
OtherDelayed Bounce - Unable to Parse Server ReasonThis is what SendGrid displays when the recipients server returns a blank reason code.

Turning off click tracking

turning-off-click-tracking page anchor

To turn off click tracking, add this to your X-SMTPAPI header:

"filters": {
"clicktrack": {
"settings": {
"enable": 0

When you try to send an invalid X-SMTPAPI header, you will get an email with details about the invalidations. You may also see errors on your Email Activity page or in your Event Webhook data. If this happens, the email should give you the information you need to begin troubleshooting. We also recommend uploading your JSON into a JSON validator, because this is often an invalid JSON issue.

Certificate verification failed for

certificate-verification-failed-for-smtpsendgridnet page anchor

"certificate verification failed for []([]:587: untrusted issuer /C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority"

If you receive this error, the connection is still encrypted; it's just that your server doesn't have the necessary CA (certificate authority) certificates to confirm that our certificate is valid.

To update your certificates:

  1. Download the GoDaddy CA bundle from takes you to an external page) (grab the one called "gd_bundle-g2-g1.crt" ).
  2. Save that on your server.
  3. Tell Postfix where to find it by adding or editing the following line in /etc/postfix/ : "smtp_tls_CAfile = /etc/postfix/ssl/gd_bundle-g2-g1.crt"
  4. Restart Postfix to make the change take effect.

If the mail server communicates with more than just us, add this certificate to your existing CA bundle (frequently called ca-bundle.crt).

550 Unauthenticated Senders Not Allowed

550-unauthenticated-senders-not-allowed page anchor

If you're getting an "Unauthenticated Senders Not Allowed" error, the problem usually lies in authenticating with our SMTP server. This error gets triggered when there was an attempt to hand over an email message through before authenticating the connection with your SendGrid username and API key.

To fix this issue, you'll want to make sure that you've configured your setup to connect to using authentication, and that the credentials you're using are your SendGrid username and a properly configured API key as the password. For more on API keys, see API Keys.

If you're using cPanel/Exim, you'll want to make sure it's configured to authenticate every time it connects to

Rate this page: