- Newest
- Most votes
- Most comments
SES will always rewrite the outgoing Message-ID, but it leaves the References header alone - so if you append the original Message-ID to References before the message hits SES, the recipient's reply will continue to carry the original Message-ID in its References chain - and Mailman's archive should be able to match the replies back to the original.
I wrote a small Postfix milter that does exactly this: milter-autoref (Docker image). It doesn't have anything in it that's specific to Mailman, but if Mailman is sending messages via Postfix which forwards to AWS SES, adding this to the Postfix installation should fix the issue. (Disclosure: I'm the author.)
This should work as long as Mailman is sending messages through a local Postfix installation, not relaying straight to SES SMTP.
answered 3 months ago
The following document shows "Message-ID" in the header field, so it is possible to send an email with the same ID.
https://docs.aws.amazon.com/ses/latest/dg/header-fields.html
As described in this document, you can use "SendRawEmail" and include "Message-ID" in the header to send an e-mail with an arbitrary value.
https://docs.aws.amazon.com/ses/latest/dg/send-email-raw.html
https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-email-format.html#send-email-concepts-email-format-header
@jcanyl very clever! In the absence of this fix, years ago, we switched to another product, but certainly wanted to use SES.
answered 3 months ago
Relevant content
asked 3 years ago
asked 3 years ago
asked 4 years ago
- AWS OFFICIALUpdated a year ago

Hi @Riku_Kobayashi, on the first link you posted https://docs.aws.amazon.com/ses/latest/dg/header-fields.html it says "If you provide a Message-ID header, Amazon SES overrides the header with its own value."