Yeah, the email address parser is very conformant.. but the SMTP parser there isn't. Had an open bug and TODO in the code to fix that forever, but just never made the cut to fix it.
There's not much of a problem with handling it there, but quoting like that makes all sorts of issues for places where you accept user input, expecting users to properly quote addresses when they type them in is really crappy ux wise. Brandon On Tue, Jun 8, 2021 at 12:58 PM Gene Hightower via mailop <mailop@mailop.org> wrote: > On 07/06/2021 11:13, Mark Milhollan via mailop wrote: > > > In general Google's MTA handles SMTP just fine. > > Well, except if you try to send from an address with a quoted-string as > the local-part: > > $ telnet gmail-smtp-in.l.google.com 25 > Trying 2607:f8b0:4023:1002::1a... > Connected to gmail-smtp-in.l.google.com. > Escape character is '^]'. > 220 mx.google.com ESMTP l10si10535546otn.151 - gsmtp > EHLO digilicious.com > 250-mx.google.com at your service, > [2600:1700:c281:3070:6a1c:a2ff:fe12:4ae6] > 250-SIZE 157286400 > 250-8BITMIME > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-PIPELINING > 250-CHUNKING > 250 SMTPUTF8 > MAIL FROM:<"a@b.c"@digilicious.com> SIZE=939 BODY=8BITMIME SMTPUTF8 > 553-5.1.7 The sender address <a@b...@digilicious.com> is not a valid > RFC-5321 > 553 5.1.7 address. l10si10535546otn.151 - gsmtp > QUIT > 221 2.0.0 closing connection l10si10535546otn.151 - gsmtp > Connection closed by foreign host. > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
