Support for assisting users whose emails are *not* bouncing, but undelivered

AI-generated summary

There is a request for adding the Queue ID of the mail server to the sent email page in the admin dashboard to track undelivered emails. supermathie suggests this would help track wayward messages that have not bounced but were not received by the end user. codinghorror mentions that a feedback ID is added to emails, but jomaxro clarifies this is added via internal hosting setup, not Discourse core. supermathie explains that adding a header would not accomplish this and proposes adding a column for the Queue ID, which would link to the full accept message when clicked, making it easier to track emails end-to-end.

Continuing the discussion from Support for contacting users whose emails are bouncing:

It would be SUPER handy to have the Queue ID of the mail server for the sent message available here to track down wayward messages which the end user has not received but which have also not bounced.

1 Like

Long long delayed answer, but don’t we add an email header for this now?

Feedback-ID: meta:user_private_message:discoursemail

No, that’s added via our internal hosting setup, not Discourse core.

2 Likes

Adding a header wouldn’t accomplish what I mean - I’m looking for another column here:

and when you click on the queue ID it would show you the full accept message:

250 2.6.0 <f4503f85-0994-476a-9a35-50c48bc6e44c@forum.example.net> [InternalId=103560258941449, Hostname=HE1EUR02HT144.eop-EUR02.prod.protection.outlook.com] 113568 bytes in 0.525, 211.090 KB/sec Queued mail for delivery -> 250 2.1.5

When Net::SMTP sends an email, it returns the queue acceptance response:

=> #<Net::SMTP::Response:0x00005625217b7888 @status="250", @string="250 2.0.0 Ok: queued as B29C51220EB\n">

For this purpose we could save string as “proof of submission” and that would make the job of tracking an email end-to-end much easier

3 Likes