[Mimedefang] RE: Large attachment timeouts

Dale_Whiteaker-Lewis at Dell.com Dale_Whiteaker-Lewis at Dell.com
Tue Jul 23 11:17:03 EDT 2002

David, can you expand on what you mean when you say it's risky?  I am
considering making the same configuration change, due to a high number of
451 tempfail messages.  

-----Original Message-----
From: Stefano McGhee [mailto:SMcGhee at ARCweb.com]
Sent: Monday, July 22, 2002 3:51 PM
To: mimedefang at lists.roaringpenguin.com
Subject: [Mimedefang] RE: Large attachment timeouts

Hello All,
>> I have done this and it seems to have really cut down on the messages 
>> getting 451'd.

>It's risky, though.

But there is another server behind it checking for viruses.  This server's
(MIMEDefang) existence is purely to block spam.  And it does it very well.
Great product!

>> Is there a way to track down the the perpetrator of the original 
>> timeouts?

>Yes.  Use the "-k" option for MIMEDefang (if you use the sample init 

>Then, if a timeout occurs, the working directory will not be deleted. 
>You can move it out of the spool and run mimedefang.pl "by hand" on 
>it, or tar it up and send it to me to look at.

I've done that before (-k and running mimedefang manually) and it seems to
confirm that it takes a long time or never finishes.  A message today timed
out, and was about 7.5MB.  After 20 min, I just gave up waiting.  I'll tar
a smaller one up and mail it to you over te next few days off list.



MIMEDefang mailing list
MIMEDefang at lists.roaringpenguin.com

More information about the MIMEDefang mailing list