There is a 120 second command timeout configured, so it would seem there was activity for about 5 seconds, then nothing for 120 seconds and the command timeout was reached causing the software to close the connection.
We’re a small operation running on Smartermail (https://www.smartertools.com/smartermail/business-email-server) and host about 5,000 mailboxes. No issues except that one of our customers has regular trouble receiving mail from bell.ca. The server runs on bare metal Supermicro with Intel NICs. Dave > On Mar 7, 2023, at 2:34 PM, Bill Cole via mailop <mailop@mailop.org> wrote: > > On 2023-03-07 at 13:35:12 UTC-0500 (Tue, 7 Mar 2023 13:35:12 -0500) > David Sovereen via mailop <david.sover...@mercury.net> > is rumored to have said: > > > [Abridged for clarity. Only the SMTP chat is left...] > >> [2023.03.06] 13:43:28.748 [204.101.223.59][57867550] cmd: RCPT TO: >> [2023.03.06] 13:43:28.748 [204.101.223.59][57867550] rsp: 250 OK Recipient ok >> [2023.03.06] 13:43:28.763 [204.101.223.59][57867550] cmd: DATA >> [2023.03.06] 13:43:28.763 [204.101.223.59][57867550] rsp: 354 Start mail >> [2023.03.06] 13:45:33.408 [204.101.223.59][57867550] rsp: 421 Command >> timeout, closing transmission channel >> [2023.03.06] 13:48:59.847 [204.101.223.59][57867550] rsp: 250 OK > > What is happening in that 125-second gap? Why are *you* timing out after 125 > seconds? > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
