I was referring to non-integrated scanning, particularly Symantec and similar products on Windows. I’ve seem SMTP handlers locked up when antivirus starts contending with spool files, etc. The right way to do that is with antivirus that hooks into the mail handler or uses a specific check directory but doesn’t seize up the whole works when an infected message comes through. If you have a scan-on-file-write antivirus doing a full scan of huge archive files each time a message comes in, it can (depending on the product and how it works) really mess the program attempting to do the writes. If you use the LISTSERV’s integrated F-Secure, this is not a problem, but non-LISTSERV-aware AV could cause issues. The same is true of inappropriate AV scanning of huge Exchange data store files and SQL database files. Yes, you need protection, but the wrong protection can be crippling. 




> On Dec 2, 2014, at 7:29 PM, Ben Parker <[log in to unmask]> wrote:
> 
> On Tue, 2 Dec 2014 21:29:27 +0000, "Sparks, Michael"
> <[log in to unmask]> wrote:
> 
>> Another thing to check is antivirus protection. Try excluding c:\listserv from scanning.
> 
> This is NOT recommended.  LISTSERV uses the directory x:\LISTSERV\TMP to
> check incoming messages for possible viruses.  Excluding this will prevent
> LISTSERV's anti-virus from working.  This is NOT recommended. 
> 
> If you want to exclude a  directory try x:\LISTSERV\LISTS (the normal parent
> directory for all list message archives).  But even this is NOT recommended
> as there may be a virus in older message archives.
> 
> ############################
> 
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1


############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1