Just to clarify, I'm not trying to pin some issue on a company (Google) but I'm trying to understand why aiosmtpd seems to follow an RFC that appears to be clear on the behavior, that GMail doesn't do but doesn't appear to be the only one (as my user is generating a document that also doesn't seems to follow it).
I'm more thinking about a different interpretation on the RFC that leads to various behavior between aiosmtpd and (some) others. Le ven. 1 mars 2024 à 18:10, Dave Crocker <d...@dcrocker.net> a écrit : > > On 3/1/2024 8:57 AM, Mark Fletcher via mailop wrote: > > You're talking about 'dot stuffing'. When you receive a message via SMTP, > in the DATA section, if you receive a line that starts with a dot (and has > additional characters after that), you remove that first dot. > > Then, when you send the message back out via SMTP, for lines that start > with a dot, you prepend a dot before sending the line on the wire. > > > Just to make sure it's clear to everyone that this is in the SMTP spec: > > RFC 5321: Simple Mail Transfer Protocol <#m_6162241132587272556_> > > 🔗 https://www.rfc-editor.org/rfc/rfc5321#section-4.5.2 > <https://www.rfc-editor.org/rfc/rfc5321#section-4.5.2> > > > > d/ > > -- > Dave Crocker > Brandenburg InternetWorkingbbiw.netmast:@dcrocker@mastodon.social > >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
