Matt wrote:
James Nelson wrote:

I'll try implementing these here in the next day or so after read up on the documentation for them. Care to explain what the size.vbs file is?


There's a lengthy discussion in the archives about that external test. Note that this requires a more recent interim release in order to run as designed, and there are also some bugs in that version that affect whether or not it will run when it's supposed to. I'll probably update that file soon, so maybe holding off would be a better idea.

If that's still not ready for use, I'll just leave it alone then.

If you are using the BOUNCE action on blocked messages (now renamed to discourage use), you should turn that off because that creates a problem for those that have had their addresses forged in spam, and those of us that try to block bounce messages from forged spam coming to our users. Regarding virus bounces, you really shouldn't bounce anything but banned extensions for similar reasons. You should read up on the newer capabilities in Declude virus to recognize forging viruses, and I encourage you to turn off (remove) the otherpostmaster.eml and sender.eml files. That seems like that number is way too high for your traffic.

Currently, we just write a header message in messages that get to a certain weight, redirect that to a special folder in the users' mailbox, and delete it after 14 days. So no bouncing of spam messages, and I've also disabled (a while ago) virus messages to sender (too many viruses forge this for it to make it useful in my opinion). Unfortunately, due to decisions beyond my control, the antivirus & spam filtering are sold as seperate services and are enabled per-user and not server wide.

Thanks for all the assistance,
::James Nelson
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to