It is annoying this is not listed in the instructions when setting up VERP. What is more irritating is that the bounce error codes are in the database but are not shown on this screen.
If you use AWS SES, then run the following query in Data Explorer:
SELECT * from email_logs where bounced=true order by id desc
Look for the column called bounce_error_code. The error code can be crossed-referenced with:
List of Enhanced SMTP Bounce Codes
- 4.2.2 - The email account is over quota
- 5.0.0 - Syntax error: invalid email address format
- 5.1.0 - Bad destination mailbox address
- 5.1.1 - Bad destination mailbox address
- 5.1.2 - Bad destination system address
- 5.1.3 - Bad destination mailbox address syntax
- 5.1.4 - Destination mailbox address ambiguous
- 5.1.5 - Destination mailbox address valid
- 5.1.6 - Mailbox has moved
- 5.1.7 - Bad sender’s mailbox address syntax
- 5.1.8 -Bad sender’s system address
- 5.1.9 - Message relayed to non-existent domain
- 5.2.0 -Other or undefined mailbox status
- 5.2.1 - Mailbox disabled, not accepting messages
- 5.2.2 - Recipient’s mailbox is full and cannot accept new messages
- 5.2.3 - Message length exceeds administrative limit
- 5.2.4 - Mailing list expansion problem
- 5.3.0 - Other or undefined mail system status
- 5.3.2 - System not accepting network messages
- 5.3.3 - System not capable of selected features
- 5.3.4 - Message too big for system
- 5.3.5 - Recipient’s mail system is misconfigured
- 5.4.0 - Other or undefined network or routing status
- 5.4.1 - Recipient’s mail server did not respond
- 5.4.2 - Problem with the connection to the recipient’s mail server
- 5.4.3 - Routing server encountered an error while delivering the message
- 5.4.4 - Message cannot be routed to the recipient’s mail server
- 5.4.5 - Network congestion is preventing delivery of the message
- 5.4.6 - Routing loop detected while delivering the message
- 5.4.7 - Message delivery time expired
- 5.5.0 - Other or undefined protocol status
- 5.5.1 - SMTP command issued by the sender is invalid
- 5.5.2 - SMTP command syntax is incorrect
- 5.5.3 - Recipient count exceeds the maximum allowed by the recipient’s mail system
- 5.5.4 - Arguments provided with the SMTP command are invalid
- 5.5.5 - SMTP protocol version used by the sender is not supported
- 5.6.0 - Other or undefined media error
- 5.6.1 - Recipient’s mail system doesn’t support the media type used by the sender.
- 5.6.2- Conversion between media types is required but prohibited.
- 5.6.3 - Conversion between media types is required but not supported
- 5.6.4 - Conversion with loss performed
- 5.6.5 - Conversion between media types failed
- 5.7.0 - Other or undefined security status
- 5.7.1 - Delivery not authorized, message refused
- 5.7.2 - Mailing list expansion prohibited
- 5.7.3 - Security conversion required but not possible
- 5.7.4 - Security features not supported
- 5.7.5 - Cryptographic operations performed by the sender failed
- 5.7.6 -Cryptographic algorithm not supported
- 5.7.7 - Message integrity failure