---------------- Only reason I did not do it before was I am afraid of blocking legit attachments of which Ive seen at least 4 or 5 get rejected that were definately legit .exe attachments and .htm attachments.
I think I'll have to loosen up some of the body checks since 1 of the rejects was an .exe file of some kind that goes to some accounting office locally. Another .exe was a local programmer who sends updates as self xtracting zip files. ------------------------ what i've done is continued to reject .exe attachments and let my users know to tell anyone that intends to send an exe to rename the exe to exx or something like that, my stance is that if the other user doesnt know enough about files and such that they cant or dont know how to rename an exe file to another extension, they probably shouldnt be sending files anyway. its worked for me, just suggest to the programmer to do just a zip instead of selfextracting, the zip as a result is smaller and anyone that needs his updates should have winzip to unzip them anyway. or of course he can just rename it to exx and the receiver can name it back to exe once they rcv it. less overhead all around. and you still have the comfort of knowing that executable files (virus') arent coming in to your network via email. my $0.02 Don
