On Tue, Jul 13, 2010 at 6:14 PM, Barbie <bar...@missbarbell.co.uk> wrote: > On Tue, Jul 13, 2010 at 05:54:05PM -0400, David Golden wrote: >> On Tue, Jul 13, 2010 at 4:00 PM, Nigel Horne <n...@bandsman.co.uk> wrote: >> > Mails being directed to spam folders can often be fixed by enabling SPF and >> > DKIM. >> > Has that been done in this case? >> >> Reverse IP for sending domain is done. SPF is implemented. DKIM is >> not. I did just see that the Message-ID still has the original >> (internal EC2 hostname) -- I'm not sure if that's the issue with the >> INVALID_MSGID. Fixing that will require either postfix rewriting the >> ID or else monkey-patching Email::MIME::Kit to override how ID's are >> generated. > > An email Message-ID can be just about anything you want it to be, as > long it's unique, and follows a basic format (see RFC 2822, section > 3.6.4 [1]). I suspect the EC2 generated Message-ID follows this format. > If not, then it might be worth posting a bug report to Amazon.
The Message-ID is generated by Email::MessageID, called from Email::MIME::Kit. (I guess email must hate the living, right, Rik?) David
