Recipients are accepted or rejected individually -- in your example, the blacklisted recipients would be accepted and the others would be accepted (assuming they passed the other filters as well).
It wouldn't be hard to add a flag to reject the entire message after seeing a single blacklisted recipient. The only scenario I can imagine where it would cause problems is: if the administrator was lazy and used the blacklist to block mail to former users instead of deleting them (e.g. ex-employees) and an external user (e.g. a client) sent a message to a group of addresses (e.g. reply-to-all). The external user would think all of the addresses were bad; there'd be no way to tell which one caused the bounce. But since enabling the flag would be optional, I guess the administrator would have only himself to blame... Anyone else have an opinion on this one? -- Sam Clippinger On 8/21/10 7:06 PM, Angus McIntyre wrote: > Apologies if this question has been asked before, or the answer > should be obvious. > > If Spamdyke detects a blacklisted address in the list of recipients, > does it kill the entire connection (thus preventing the message being > delivered to any recipient), or does it accept the message for the > non-blacklisted recipients? > > I ask this because many spammers will send spam to a batch of > addresses, which may contain a mix of bogus and legitimate addresses. > The presence of a bogus address in the list of recipients is often a > reliable clue that the message is spam, so it might be useful if > spamdyke would kill the whole message in that case. > > Angus > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
