Thanks

I'll check those settings :) 

Is there anyway to bypass the ClamWall Daemon for 1 specific email ? 

ie:

email from a specifc external address to a specifc internal user - then bypass clamwall ??

Thanks

There are no settings in ClamWall for this. Why is it that you want to make an exception for this sender? Are the messages always extremely big, or should he be allowed to send attachments that otherwise are blocked by ClamWall?

/Rolf 

Its a backup from a local server that is sent via email.
The from and to addresses are always the same.

The attachment is around 40MB (this is growing daily) so it slows the whole server down whilst it's scanned.

This seems horribly inefficient, wouldn't you be better to have a script (s)FTP it instead?

Right, this will soon become unmanageable even without virus scanning. SMTP isn't good for sending huge amounts of data, so if at all possible a FTP solution would be much better.

If you really really must use email for this you could consider setting up a second instance of Mercury that listens on another port for incoming SMTP and doesn't use ClamWall. The IP number of your remote server could be the only one allowed to connect via SMTP to this Mercury instance.

/Rolf 

Thanks.

I'm going to look at using FTP. 

If you haven't changed the StreamMaxLength setting in the ClamD.conf file, ClamD scans only the first 10mb of a file anyway (if it's an archive the ArchiveMaxFileSize setting applies instead) so the scanning time will not increase if the size grows.

Best regards


Nico