SES does not allow the caller to set the id of the message and instead assigns one when you make the call.
It is a bit painful for idempotency.
It is a bit painful for idempotency.
Perhaps SMTP could use an extension with a new (pipelined) command after DATA, so a client can retrieve the assigned message-id.
I wonder how common it is for message-id's to be overwritten. I must have run into this SES behaviour (along with other problems) when trying to use it as backup for outgoing mail for my mail server: My DKIM signatures include the message-id header, overwriting the header will invalidate them.