I have some customers that wish to not have their email scanned for spam. I started off whitelisting them, but this presents two problems:A per-user config would likely be the best option in this case. The problem is that E-mail with Cc:'s or Bcc:'s must be handled the same for each recipient -- so whatever happens for one recipient will happen for the others. With whitelisting (which takes priority over everything else), it would cause the spam to get through to the other recipients. However, by setting up a per-user configuration that doesn't take any action on E-mail, the E-mail with multiple recipients will still get filtered. The E-mail with multiple recipients is essentially "shared" (the sender *knows* that), so you need to decide how the recipients share it (whether to whitelist it, or block it).
1. Some spam gets through to others because of their whitelist. Ex. Someone sends spam to [EMAIL PROTECTED], but in the CC, there's [EMAIL PROTECTED] [EMAIL PROTECTED] is whitelisted, so the mail gets delivered to me with a weight of 0 (whitelisted).
2. You can only have 200 whitelist entries.
Now, creating a per-user config for the user, and setting all actions to warn, would that not effectively disable spam filtering?
-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.
