On Fri, 30 Apr 2010 15:23:41 -0400 Ed Szynaka <szyn...@localnet.com> wrote:
[...] > > The README contradicts that > > --classify > Tells DSPAM only to classify the message, and not make any writes to the > user's metadata or attempt to deliver/quarantine the message. > > NOTE: The output of the classification is specific to the user, not > including > the output of any groups they might be affiliated with, so it is > entirely possible that the message would be caught as spam by the > group, > even if it didn't appear in the classification. If you want to get > the classification for the GROUP, use the group name as the user > instead of an individual. > For merged groups this is not working that way. I have to consult the code to see if this is the case. For shared or shared,managed groups one can check the group to get the final result. But for merged group the user tokens are merged at runtime with the group tokens and just checking user tokens might have another result then just checking the group tokens and yet another result if you check the user incl. his group membership. > Also where would I look in the debug output to find which set of tokens > determined the final result? In my debugs I only see if a user is included > in a > group but not whether the user or CLASSIFICATION group data was used for the > final result. > Take the last patch I have send you. That should print out more info. > > -- > Ed Szynaka > Network/Systems Manager > LocalNet Corp./CoreComm Internet Services > -- Kind Regards from Switzerland, Stevan Bajić ------------------------------------------------------------------------------ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
