Moin
On Mon, Nov 29, 2021 at 01:57:54PM -0800, Michael Peddemors via mailop wrote:
> No, Pipeline is not advertised, the RFC's say that when you send a command,
> if you are NOT using pipelining, you need to wait for a response, and that
> includes the QUIT.. wait for the receiving system to send
It appears that Bill Cole via mailop said:
>SMTP clients of all sorts have done this (and worse, e.g. just FIN after
>getting a 250 at end-of-data) for at least 3 decades. I don't see how it
>could possibly be useful at this late date to try to enforce that SHOULD
>which only exists for a
On 2021-11-29 at 20:00:14 UTC-0500 (Mon, 29 Nov 2021 17:00:14 -0800)
Michael Peddemors via mailop
is rumored to have said:
It does sound like you are arguing for dropping QUIT altogether,
Nope. I didn't say that or anything like that. QUIT is essential. The
response to QUIT is superfluous.
On 2021-11-30 09:00:14 (+0800), Michael Peddemors via mailop wrote:
On 2021-11-29 3:20 p.m., Bill Cole via mailop wrote:
Michael Peddemors via mailop is rumored to have said:
No, Pipeline is not advertised, the RFC's say that when you send a
command, if you are NOT using pipelining, you need
On 2021-11-29 3:20 p.m., Bill Cole via mailop wrote:
On 2021-11-29 at 16:57:54 UTC-0500 (Mon, 29 Nov 2021 13:57:54 -0800)
Michael Peddemors via mailop
is rumored to have said:
On 2021-11-29 6:57 a.m., Larry M. Smith via mailop wrote:
On 11/24/2021, Michael Peddemors via mailop wrote:
CONN:
On 2021-11-29 at 16:57:54 UTC-0500 (Mon, 29 Nov 2021 13:57:54 -0800)
Michael Peddemors via mailop
is rumored to have said:
On 2021-11-29 6:57 a.m., Larry M. Smith via mailop wrote:
On 11/24/2021, Michael Peddemors via mailop wrote:
CONN: 40.107.96.87 -> 25 GeoIP = [US] PTR =
On 2021-11-29 6:57 a.m., Larry M. Smith via mailop wrote:
On 11/24/2021, Michael Peddemors via mailop wrote:
CONN: 40.107.96.87 -> 25 GeoIP = [US] PTR =
mail-sn1anam02on2087.outbound.protection.outlook.com OS = Windows NT
kernel
Returning 250 ok [qp 3539411] for data
QUIT command received,
On 11/24/2021, Michael Peddemors via mailop wrote:
CONN: 40.107.96.87 -> 25 GeoIP = [US] PTR =
mail-sn1anam02on2087.outbound.protection.outlook.com OS = Windows NT kernel
Returning 250 ok [qp 3539411] for data
QUIT command received, args:
And then it terminates the connection, SSL collapses,
I am not criticizing qmail for this behaviour. If you need another
example:
The Postfix smtp(8) client normally does not wait for the server's
reply to the QUIT command, and it never waits for the TCP final
handshake to complete.
So now you have two people, who know that they are doing, having
Umm.. not helpful, and if you are going to make inflammatory remarks, please
sign it with your name..
Really isn't fair to call out Qmail, Dan Bernstein did an incredible amount of
good in his day, and what version of Qmail are you using? Tell me if you see
this happening in your logs, and if
On Wed, Nov 24, 2021, Michael Peddemors via mailop wrote:
> And then it terminates the connection, SSL collapses, without waiting for
> the remote mail server to acknowledge the QUIT.
Just like qmail?
Maybe it's time to change the RFC?
___
mailop
CONN: 40.107.96.87 -> 25 GeoIP = [US] PTR =
mail-sn1anam02on2087.outbound.protection.outlook.com OS = Windows NT kernel
Returning 250 ok [qp 3539411] for data
QUIT command received, args:
And then it terminates the connection, SSL collapses, without waiting
for the remote mail server to
12 matches
Mail list logo
