It's usually better to filter by IP, unless you see E-mail coming from the same domain a lot (such as is the case with the "from $domain" spammer). However, you can create a filter such as "HELO 5 CONTAINS .330w.com" to catch E-mail from servers claiming to be *.330w.com.1. What is the best way to use the Received: field. Example:Received: from sandra.330w.com [216.53.71.180] What I'd like to do is bounce everything from *.330w.com. Is this poor practice? Should I really filter by IP?
2. I as an administrator find the header information very useful, but my usersThat's up to the mail client to handle. Some mail clients show no headers by default, some show all headers, and some show all headers with the exception of the most common headers.
don't. Is there a way to hide the extra Declude headers on certain accounts,
or disable the Declude headers on all but a few accounts?
The generic Declude headers (the ones listed in the global.cfg file, such as the X-Declude-Sender: header) are global options, and can not be enabled/disabled by domain. The X-RBL-Warning: headers are based on the WARN action, and can be turn off for certain users if necessary by using the per-user settings.
-Scott
---
[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.
