Bounced Email Info Not Found

Support
1

I went to investigate a user who did not receive an email for signing up. The admin screen showed a bounced score. I went to Admin->Email->Server setup & logs->Bounced(tab).

I see the user listed on the Bounced report. When I click on the information icon for additional info, the following appears.

The image shows a user interface with an error message stating "An error occurred: Discourse:NotFound" overlaid on a partially visible form for viewing incoming email details, with an "OK" button to dismiss the alert. (Captioned by AI)
The image shows a user interface with an error message stating "An error occurred: Discourse:NotFound" overlaid on a partially visible form for viewing incoming email details, with an "OK" button to dismiss the alert. (Captioned by AI)769Ă—532 8.86 KB

Any suggestions or ideas on how to resolve this?

Supporting Info:

  1. Running 3.5.0.beta2-dev (f591083407)
  2. Using AWS SES for mail delivery with VERP installed.
  3. Everything is working except the bounce info.
2 Likes
4

Would someone mind checking if your system is working and if it is just my system with the problem?

I have looked into the table called Email_Logs. This shows a bounce key and bounced error code. Does anyone know where to look at the specific email info? Header, body, etc?

5

I’m not sure about what I’m going to write :eyes:, but I think by default SES doesn’t log such information. Other email services do.
Perhaps you can try to enable it and see what reason is given for the bounced email from SES’s interface?

2 Likes
6

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
2 Likes
8

You’re right, this isn’t a great experience.

How do you have your site configured to process bounces? Is it receiving the information via a web hook but without the actual mail?

3 Likes
10

I followed the instructions for AWS SES on this page: Configure VERP to handle bouncing e-mails.

So, yes, we are using the standard webhook.

I do not have the “enable raw message delivery” option activated. I will activate this to see if it sends the entire message. This is not a requirement in the installation documentation, but other posts have listed it as a requirement.

2 Likes
11

I think (I’m VERY familiar with email bounces, not as much with the incoming webhooks) that without that option checked we get only minimal information about the bounce, so that makes sense.

I’ve asked the responsible team to look at improving this experience; when we don’t have the raw bounced email, we should at least be able to tell you the information we do have.

3 Likes