I think clicking on an “Email Type” field, e.g. user_watching_first_post is meant to display details of the bounce message received from the intended recipient. But on my self-hosted site I get the error message stated above. Is there anything I can do to fix this? Thanks.

I have upgraded both and still get the same error, including (I think) for emails received since the upgrade. Any further ideas?

Same problem here. Self-hosted, up to date. Bounces being handled the recommended way. Links from before we changed to proper bounce handling work fine.

[image] simon: I’m wondering is the issue is related to how your mail server handles forwarding the bounce message. Yes likely Discourse isn’t getting it from Mailgun. I don’t know how the webhooks work but suspect it just tells Discourse there has been a temporary/permanent failure without sending the bounce message.

Is there any way to make this Discourse feature work with Mailgun? It should be possible to show at least the error code and message: Both SMTP error code and SMTP error message are preserved “code”: 550, “address”: “'baz@example.com”, “error”: “Message was not accepted – invalid mailbox. Local mailbox 'baz@example.com is unavailable: user not found” https://documentation.mailgun.com/en/latest/api-bounces.html#examples If not then at least we need a sensible error message to explain why the link doesn’t work :slight_smile:

Has any work been done on this. I’d be very grateful if there had :slight_smile: I use Digital Ocean and Mailgun (ie the main recommendations) so imagine it’s not just me with the problem.

After my own testing it seems in many cases, bounces are not received by the mail receiver at all. (I only found a connection attempt for one, which was promptly lost). I’m not seeing the Return-Path header being set at all (is it supposed to be?) which makes me think that they’re not even being sent back most of the time.

Still a problem here as well. Despite my earlier statement, it now appears that none of these links work, going back to site startup. Initially it only seemed to affect bounces from before we started handling bounces properly (Configure VERP to handle bouncing e-mails).

I’ve just noticed stacks of warnings in the error log along these lines: Email can not be processed: Email::Receiver::AutoGeneratedEmailError Received: from ... for ; ... Subject: Your message couldn't be delivered Perhaps this is why Discourse doesn’t have any details for the bounced emails.

I’m not seeing those errors in the logs, but the problem persists. When I click the Email Type value for an entry in the Bounced email list, I get “An error occurred: Discourse::NotFound”.

[image] Jeff Rivett: I’m not seeing those errors in the logs What if you tick “Warning”? [image]

"Discourse::NotFound" error when click "Email Type" field on admin/email/bounced

Product Support Self-hosting

jrivettcsa (Jeff Rivett) March 1, 2023, 11:44pm 20

Agreed. If something isn’t actually broken, it should not appear to be broken. Discourse can surely provide a more reassuring message.

Topic		Replies	Views
Bounced Email Info Not Found Product Support email	6	344	March 24, 2025
Bounced emails not being detected Product Support email	16	1865	February 7, 2024
Amazon SES/SNS email complaints not received, bounces missing information Self-hosting email	5	1677	April 6, 2023
Configure VERP to handle bouncing e-mails Self-Hosting email , how-to	10	32942	July 30, 2026
Where do I find details about bounced emails in Discourse? Product Support	7	1857	December 18, 2020

"Discourse::NotFound" error when click "Email Type" field on admin/email/bounced

Related topics