News for hackers. Stuff that matters.

A comment on Trap and test AWS SES emails locally. Parent comment

Re:Trap and test AWS SES emails locally by wiml on Monday November 20, 2023 @03:48AM (#38344944)
Hm, many MTAs do return a unique queue ID when they accept a message over SMTP. Does SES not implement that?
[ Parent | on HN ]
Re:Trap and test AWS SES emails locally by sethammons on Monday November 20, 2023 @05:48AM (#38346109)
Any examples? Curious how they do it. Just extra info in the 250 OK response to the DATA command?
[ Parent | on HN ]
Re:Trap and test AWS SES emails locally by meepmorp on Monday November 20, 2023 @07:29AM (#38347031)
RFC 822 defines a Messsge-id header that the client can set, and most MTAs can be configured to add one if not set by the client. IIRC, they're supposed to be globally unique, but like so many things in email, ymmv.

Edit: oh, yeah, there's also a queue id returned in the 250 response (in postfix, at least)

[ Parent | on HN ]
Re:Trap and test AWS SES emails locally by wiml on Monday November 20, 2023 @08:14PM (#38357452)
Yeah, just in the text of the OK response. So I guess it isn't really very structured. Seems like it would be a useful ESMTP capability to add though - queue identifier and MTA-assigned message-ID.
[ Parent | on HN ]