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 wh
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.go
On 6/7/2021 1:13 PM, Mark Milhollan via mailop wrote:
(snip)
> In general Google's MTA handles SMTP just fine. But an MTA isn't always
> run in a way that blindly follows the RFCs.
>
> Some have learned that a 5xx code isn't always a permanent problem
> though the extended code (5.x.x) and/or the
On 6/7/2021 2:08 PM, Thomas Walter via mailop wrote:
(snip)
> And there's also systems that send a 5xx and immediately disconnect
> without waiting for the "quit" from the initiating party to properly
> terminate the SMTP session.
>
> In those cases MTAs following the RFCs see this as a failed con
Hello,
Thomas Walter via mailop wrote on 07.06.21 at 21:08:
And there's also systems that send a 5xx and immediately disconnect
without waiting for the "quit" from the initiating party to properly
terminate the SMTP session.
In those cases MTAs following the RFCs see this as a failed connectio
'llo,
On 07.06.21 20:13, Mark Milhollan via mailop wrote:
> In general Google's MTA handles SMTP just fine. But an MTA isn't always
> run in a way that blindly follows the RFCs.
And there's also systems that send a 5xx and immediately disconnect
without waiting for the "quit" from the initiating
On Sun, 6 Jun 2021, Larry M. Smith wrote:
Seems that gmail.com's MTA can't properly speak SMTP. I've been seeing
re-queuing and re-sending of permanent failures for some time now,
Delivery incomplete
There was a temporary problem delivering your message to [redacted].
Gmail will retry for 47
On 06/06/2021 16:33, Noel Butler via mailop wrote:
> Those who live in terribly fragile glass houses, shouldn't ever cast stones
I apologize if it seemed that I was casting stones, I was actually
attempting to help out.
___
mailop mailing list
mailop@m
On 07/06/2021 05:14, Gene Hightower via mailop wrote:
On 06/06/2021 07:34, Larry M. Smith via mailop wrote:
Seems that gmail.com's MTA can't properly speak SMTP. [...]
$ telnet imp.fahq2.com smtp
Trying 47.12.77.216...
Connected to imp.fahq2.com.
Escape character is '^]'.
220 "helob0gus.fah
On 6/6/2021 2:01 PM, Gene Hightower wrote:
> On 06/06/2021 07:34, Larry M. Smith via mailop wrote:
>
>> Seems that gmail.com's MTA can't properly speak SMTP. [...]
>
> $ telnet imp.fahq2.com smtp
> Trying 47.12.77.216...
> Connected to imp.fahq2.com.
> Escape character is '^]'.
> 220 "helob0gu
On 06/06/2021 07:34, Larry M. Smith via mailop wrote:
> Seems that gmail.com's MTA can't properly speak SMTP. [...]
$ telnet imp.fahq2.com smtp
Trying 47.12.77.216...
Connected to imp.fahq2.com.
Escape character is '^]'.
220 "helob0gus.fahq2.com ESMTP"
The syntax of the initial greeting offered
Seems that gmail.com's MTA can't properly speak SMTP. I've been seeing
re-queuing and re-sending of permanent failures for some time now, but
now I'm seeing its user simply hitting forward and sending the bounce to
the original failed recipient.
.. I do get pretty worked up by not being able to f
12 matches
Mail list logo
