If a message is addressed to multiple TO recipients all on the same host, and one or more of those recipients has a custom JunkMail configuration, how does Declude determine which configuration to use for processing the message?
 
I have a user who does not want her account scanned by JunkMail at all.  She got a touch upset recently, thought her account was being scanned again.  What appears to have happened is that she got a couple spam-wrapper messages on which there were multiple recipients, with three different JunkMail configurations among those recipients:
 
ONE recipient has "SUBJECT Possible Spam" on Weight10, and "ATTACH Probable Spam" on Weight14 or higher, which is apparently the configuration used to process the messages in question.
 
ONE of the recipients (her) has a configuration with all tests disabled.
 
The rest of the recipients have the "default" configuration for the host, which is "SUBJECT Possible Spam" on Weight14 or Weight20, and DELETE on Weight30.
 
Does Declude use the most restrictive configuration it finds among all the recipients?  One message had a spam value of 16 and one had 27, both high enough to trigger the Weight14 ATTACH for that particular recipient's configuration.
 
I'm running Declude 1.53.
 
Glenn Z.
 

Reply via email to