Maximum Archive Depth causing MailScanner to crash

Scott Silva ssilva at sgvwater.com
Fri Oct 12 00:36:00 IST 2012


on 10/11/2012 3:26 PM Paul Welsh spake the following:
> Hi all
> 
> Currently I have MailScanner 4.84.5 .conf set to:
> Maximum Archive Depth = 0
> 
> However, this means that filename and filetype checks aren't being
> done on *.exe files in *.zip files so I changed it to:
> Maximum Archive Depth = 3
> which I believe is the default.
> 
> Unfortunately, this caused MailScanner to crash and restart each time
> it came across a *.exe file in a *.zip file.  Instance after instance
> of MailScanner started and went defunct in a constant loop.
> 
> I tried using:
> Archives: Filename Rules = %etc-dir%/archives.filename.rules.conf
> 
> I also tried this on its own:
> Archives: Deny Filenames = \.exe$
> 
> I changed it back to:
> Maximum Archive Depth = 0
> and all went back to normal.
> 
> Any ideas what could be going wrong?
> 
> Regards
> 
> Paul
> 
Do a MailScanner --v and see if you have missing modules or old versions





More information about the MailScanner mailing list