[Mimedefang] Broken Pipe in Milter?

[Dale_Whiteaker-Lewis at Dell.com]

Thanks.  8.12.5 w/MD 2-15 w/SpamAssassin 2.31 doesn't seem to do the trick.
I get a ton of "client didn't issue EXPN" etc. type messages as well and no
messages are processed.  Curiouser and curiouser...  

Example maillog snippet:
Jul  6 23:02:37 smtp6 sendmail[27892]: g6742a3J027892: [211.251.148.129] did
not 
issue MAIL/EXPN/VRFY/ETRN during connection to MTA
Jul  6 23:02:37 smtp6 sendmail[27893]: g6742a3J027893: [211.251.148.129] did
not
 issue MAIL/EXPN/VRFY/ETRN during connection to MTA
Jul  6 23:02:37 smtp6 sendmail[27894]: g6742a3J027894: [211.251.148.129] did
not 
issue MAIL/EXPN/VRFY/ETRN during connection to MTA
Jul  6 23:02:37 smtp6 mimedefang-multiplexor: Starting slave 0 (pid 27896) 
(1 running): Bringing slaves up to minSlaves
Jul  6 23:02:37 smtp6 mimedefang-multiplexor: Reap: Idle slave 0 (pid 27896)

exited normally with status 1 (SLAVE DIED UNEXPECTEDLY)
Jul  6 23:02:38 smtp6 sendmail[27895]: g6742b3J027895:
from=<kvlci at hotmail.ru>, 
size=4893, class=0, nrcpts=2,
msgid=<200207070402.g6742b3J027895 at smtp6.us.dell.com>, 
proto=ESMTP, daemon=MTA, relay=[61.79.122.226]


Clues, anybody? 

-----Original Message-----
From: David F. Skoll [mailto:dfs at roaringpenguin.com] 
Sent: Saturday, July 06, 2002 1:23 PM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] Broken Pipe in Milter?


On Sat, 6 Jul 2002 Dale_Whiteaker-Lewis at Dell.com wrote:

> Did anyone ever solve the problem with the following error, mentioned 
> in 
>
http://lists.roaringpenguin.com/pipermail/mimedefang/2002-February/000405.ht
ml?
> I'm desparately trying to solve the same problem for my large company,
it's
> only happening on one machine.  I'm running RH 7.3 and MD 2.5, Sendmail
> 8.12.1

Upgrade your sendmail -- all versions prior to 8.12.3 (I think) have buggy
milter implementations.  The latest version is 8.12.5.  Be sure to rebuild
MIMEDefang against the latest libmilter, too.

Also, some of these "broken pipe" messages are normal.  Often, if the peer
times out or breaks the SMTP connection, you'll get the message. So if it
happens once in a while, it's probably OK.  If it happens a lot, there's a
problem.

Regards,

David.

_______________________________________________
MIMEDefang mailing list
MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang