Bowie Bailey said: > I have been seeing quite a few errors like this in my logs recently > (633 of them yesterday). Most of them are like the first example. > What are they and how do I investigate them further (if I need to)? > > Nov 11 04:04:19 bnofmail courieresmtpd: writev: Broken pipe > Nov 11 05:23:14 bnofmail courieresmtp: > id=0063C0B4.419283A8.00000CCA,from=<#############>,addr=<###############>: > Broken pipe
Those errors are the result of the other end closing the connection at a time when courier does not expect it. This can happen in a few situations. 1) The other MTA directly drops the connection after saying QUIT. This is actually quite common and courier is the only MTA complaining about it. This behaviour (the dropping of the connection) violates a RFC SHOULD, but it is said to be more efficient by it's proponents. 2) It can happen because of a monitoring system just opening the connection and then closing it. 3) Some spamware is so badly written, it provokes this error. 4) Some network error closed the connection unexpectedly. Learn to live with it, or write a patch (I did, but I lost it :-( ). HTH, M4 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
