4 ms·
Buy me a drink and I'll tell you about the time I investigated a service that, among other things, sent email with a Message-ID based on the date. (Not the time
by billpg 6y ago
Buy me a drink and I'll tell you about the time I investigated a service that, among other things, sent email with a Message-ID based on the date. (Not the time of day.)
It was meant to send one email every day. Until it wasn't.
- theamk 6y agoThis just looks like a broken sender - I mean, RFC5322 is pretty clear that "The generator of the message identifier MUST guarantee that the msg-id is unique." I know that practically, we want to support every email out there, even if it is not quote RFC compliant -- but how far do we want to go? Is it worth adding all new mechanism just because someone out there may be sending non-compliant messages? Especially given that those non-compliant messages are likely to break other things like mail databases, IMAP UIDVALIDITY and so on?