On 2014-11-24 15:20, Benny Kurniawan Candra wrote: > Fri 2014-11-21 15:23:32: 06: [781039] * Message is clean (no viruses found) > Fri 2014-11-21 15:23:32: 06: [781039] ---- End AntiVirus results Fri > 2014-11-21 > 15:23:33: 04: [781039] Socket error sending response to DATA Fri 2014-11-21 > 15:23:33: 04: [781039] * Winsock Error 10054 Fri 2014-11-21 15:23:33: 04: > [781039] SMTP session terminated (Bytes in/out: 20887/543) > > > The error Windows Socket Error 10054 happened after the email passed > antivirus check on receiver’s side. It is obvious that the issue is on the > non-Office 365 > receiver’s side.
The antivirus already finished the scanning and ready to receive DATA, but not fast enough to response the DATA transmitted by sender that's trigger winsock error 10054. If sender follow Internet Mail Regulation, it should wait till MDaemon (receiver) issue 354 Enter mail, end with <CRLF>.<CRLF> before transmit the DATA. Because the DATA transmission failed, sender (client) have responsibilities retry to send till success or failure in between 2-5 days. http://msdn.microsoft.com/en-us/library/aa924071.aspx 10054 WSAECONNRESET Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt (Windows Sockets) for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. https://tools.ietf.org/html/rfc5321#page-62 4.5.3.2.4. DATA Initiation: 2 Minutes This is while awaiting the "354 Start Input" reply to a DATA command. 4.5.4.1. Sending Strategy The sender MUST delay retrying a particular destination after one attempt has failed. In general, the retry interval SHOULD be at least 30 minutes; however, more sophisticated and variable strategies will be beneficial when the SMTP client can determine the reason for non-delivery. Retries continue until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days. It MAY be appropriate to set a shorter maximum number of retries for non- delivery notifications and equivalent error messages than for standard messages. The parameters to the retry algorithm MUST be configurable. -- syafril ------- Syafril Hermansyah MDaemon-L Moderators, running MDaemon 14.5.2-64, SP 4.5-64 Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. There are three kinds of men. The ones that learn by readin’. The few who learn by observation. The rest of them have to pee on the electric fence for themselves. --- Will Rogers -- --[MDaemon-L]------------------------------------------------ Milis ini untuk Diskusi antar pengguna MDaemon Mail Server. Netiket: http://www.netmeister.org/news/learn2quote Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com Versi terakhir MD 14.5.1, SP 4.5, BES 2.0.2, OC 3.0, SG 3.0.2
