Authentication successful
235 Authentication successful
Your SMTP client successfully connected and signed in to the SMTP server.
Successful delivery
250 Ok
MessageID
MessageID
is a unique string of characters that Amazon SES uses to identify a message.
Service unavailable
421 Too many concurrent SMTP connections
Amazon SES can't process the request because there are currently too many connections to the SMTP server.
Local processing error
451 Temporary service failure
Amazon SES couldn't process the request. There might be issues with the request that prevent it from being processed.
Timeout
451 Timeout waiting for data from client
Too much time elapsed between requests, so the SMTP server closed the connection.
Daily sending quota exceeded
454 Throttling failure: Daily message quota exceeded
You've exceeded the maximum number of emails that Amazon SES permits you to send in a 24-hour period. For more information, see Managing your Amazon SES sending limits.
Maximum send rate exceeded
454 Throttling failure: Maximum sending rate exceeded
You've exceeded the maximum number of emails that Amazon SES permits you to send per second. For more information, see Managing your Amazon SES sending limits.
Amazon SES issue when validating SMTP credentials
454 Temporary authentication failure
Issues that could cause this issue include (but aren't limited to):
Problem receiving the request
454 Temporary service failure
Amazon SES didn't successfully receive the request. As a result, the message wasn't sent.
Incorrect credentials
530 Authentication required
The application that you use to send email didn't attempt to authenticate when it connected to the Amazon SES SMTP interface.
Authentication Credentials Invalid
535 Authentication Credentials Invalid
The application that you use to send email didn't provide the correct SMTP credentials to Amazon SES. Note that your SMTP credentials aren't the same as your AWS credentials. For more information, see Obtaining Amazon SES SMTP credentials.
Account not subscribed to Amazon SES
535 Account not subscribed to SES
The AWS account that owns the SMTP credentials is not signed up for Amazon SES.
Message is too long
552 Message is too long.
The message that you're trying to send is larger than the maximum message size.
Account not subscribed to Amazon SES
535 Account not subscribed to SES
The AWS account that owns the SMTP credentials is not signed up for Amazon SES.
MAIL FROM syntax error
553 <
email-address
> Invalid email address
There is a syntax error in the MAIL FROM part of the SMTP message. Please check that you are following the correct format and don't forget to enclose the email-address in '<>'.
RCPT TO syntax error
553 <
email-address
> address unknown
There is a syntax error in the RCPT TO part of the SMTP message. Please check that you are following the correct format and don't forget to enclose the email-address in '<>'.
User not authorized to call the Amazon SES SMTP endpoint
554 Access denied: User
UserARN
is not authorized to perform ses:SendRawEmail on resource IdentityARN
The AWS Identity and Access Management (IAM) policy or the Amazon SES sending authorization policy of the user who owns the SMTP credentials isn't allowed to call the Amazon SES SMTP endpoint.
Unverified email address
554 Message rejected: Email address is not verified. The following identities failed the check in region
region
: identity0
, identity1
, identity2
You're trying to send email from an email address or domain that isn't verified to send email from your Amazon SES account. This error could apply to the "From", "Source", "Sender", or "Return-Path" addresses. If your account is still in the sandbox, you also have to verify every recipient email address (except for the recipients provided by the Amazon SES mailbox simulator). If Amazon SES isn't able to show all of the identities that failed the verification check, the error message ends with three periods (...).
NoteAmazon SES has endpoints in several AWS Regions, and email address verification status is separate for each AWS Region. You have to complete the verification process for each sender in the AWS Regions that you want to use.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4