RE: SOLVED: SMTP transaction interrupted

Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285 80.74.176.142.25 217.11.85.59.2528: . ack 1998901 win 32767 nop,nop,sack sack 1 {1994821:1996181} (DF) What happens is that the receiver

SOLVED: SMTP transaction interrupted

I think I have solved the mystery. But I can offer you only a workaround, to turn off selective ACK support. Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285 80.74.176.142.25 217.11.85.59.2528: . ack 1998901

Re: SOLVED: SMTP transaction interrupted

Rocco Scappatura: I think I have solved the mystery. But I can offer you only a workaround, to turn off selective ACK support. Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285 80.74.176.142.25

RE: SOLVED: SMTP transaction interrupted

I think I have solved the mystery. But I can offer you only a workaround, to turn off selective ACK support. Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285 80.74.176.142.25 217.11.85.59.2528: .

Re: SOLVED: SMTP transaction interrupted

Rocco Scappatura: I think I have solved the mystery. But I can offer you only a workaround, to turn off selective ACK support. Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285 80.74.176.142.25

Re: SOLVED: SMTP transaction interrupted

Rocco Scappatura: I think I have solved the mystery. But I can offer you only a workaround, to turn off selective ACK support. Here is one event in a tcpdump file that I received a few hours ago (full context is below the signature): 10:49:57.930285

Re: SOLVED: SMTP transaction interrupted

Wietse Venema: I don't know if this is a problem with Windows TCP/IP, or if this is a problem with a firewall on the client side. Reportedly, some firewalls randomize TCP sequence numbers but don't update the sequence numbers in SACK fields. That would be a sure way to mess up TCP. Quoting

Re: SOLVED: SMTP transaction interrupted

Wietse Venema wrote: Wietse Venema: I don't know if this is a problem with Windows TCP/IP, or if this is a problem with a firewall on the client side. Reportedly, some firewalls randomize TCP sequence numbers but don't update the sequence numbers in SACK fields. That would be a sure way