Ugh, those timeouts are insane, from a different era. Brandon
On Tue, Nov 14, 2017 at 10:58 AM Renaud Allard via mailop <mailop@mailop.org> wrote: > > > On 14/11/2017 16:51, Jeremy Harris wrote: > > On 14/11/17 13:16, Vladimir Dubrovin via mailop wrote: > >> > >> Timeout after "." on smaller messages and in the middle of transmission > >> on large-size messages usually mean TCP connection issues, most common > >> reason is PMTUD blackhole router problem. > > > > On any size message they can be due to a too-small timeout on the > > client end (five _minutes_ per standards, I think) and content scanning > > done on the server end (the content not being available for scan until > > it has all arrived). > > > > Actually, it's way more than that: > Initial 220 Message: 5 Minutes > MAIL Command: 5 Minutes > RCPT Command: 5 Minutes > DATA Initiation: 2 Minutes > Data Block: 3 Minutes. This is while awaiting the completion of each TCP > SEND call transmitting a chunk of data. > DATA Termination: 10 Minutes > > So the minimum timeout for 1 message is about 30 minutes. That said, > many systems don't wait that long, unfortunately. > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
