ok, so next question... if declude caught the attachment why did it not list with the %BANEXT% variable? That variable was blank. How would I determine what file extension was caught. I'm just trying to understand...
On Friday, August 9, 2002 9:17 AM, R. Scott Perry <[EMAIL PROTECTED]> wrote: >Those headers won't affect whether or not Declude bans the files -- the >*real* filename is one you won't see, becaues it is encoded. > >You can send a copy of the E-mail file to [EMAIL PROTECTED] , and I can >test it here to see what the real extensions are. > -Scott > >At 11:11 AM 8/9/2002, you wrote: > >> >The catch here is that BinHex (Mac encoding) files have the filename within >> >the encoded segment. So you can have a situation where the MIME filename >> >is "safefile.txt", but the BinHex segment says the filename is >> >"evilvirus.exe" (which you won't see, because it is encoded). >> > -Scott >> > --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
