Doug Traylor wrote:
> ASSP can not decode uuencoded emails which is how many of these are being
> sent. It can not block based on attachment type if it can not see what is
> in the email. Some of those will get caught by ClamAV if you are using that
> with ASSP, but not all, as it comes down to how new are your signature files
> and does Clam even have a solution for that particular file. At this time
> ASSP file blocking is not absolutely reliable for this reason.
You can use this to block all UUENCODED attachments:
\bbegin\b \d\d\d \b\S{0,72}.*(\S{61}).{0,61}\bend\b# UUECODED attachment
I have been blocking them since I first posted about this problem (dunno
how far back that was, but its in the archives). I have not heard a
single complaint. No modern email clients use UUENCODE.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
