I've been thinking about this for a while. Scott... how hard would it be for Declude to split the message when faced with a conflict like this.
Specifically, if a message fails at the global level, but a domain has it whitelisted then a copy of the message is created that removes the other recipientst - so that the message can be delivered to the one domain where it is desired. Similarly, if blocked at the domain level and if a single user has the message white listed then a copy of the message would be created with the single user as the addressee so that they can receive the message. I would think that the conflict would be easy to detect, that a new copy of the message could be created in queue with the appropriate address(es), and that the original to, cc, & bcc headers could be aliased with a specail x- header. This is an analog of a feature on our development list for the sortmonster mail engine, but I'll be you could implement it in IMail/Declude without much trouble. Am I wrong? _M | -----Original Message----- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]] On Behalf Of R. | Scott Perry | Sent: Monday, February 10, 2003 1:43 PM | To: [EMAIL PROTECTED] | Subject: Re: [Declude.JunkMail] Whitelist Question | | | | >I have some customers that wish to not have their email scanned for | >spam. I started off whitelisting them, but this presents | two problems: | > | >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? | | 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). | -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. --- [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.
