Stevan Bajić wrote: >> I've added the following to the group file: >> corpususer:classification:*corpususer >> > That is IMHO not correct. The line should probably be: > corpusgroup:classification:*corpususer >
Yes that's how the README lists it as well. The only reason I tried the variations was to attempt to get the debug to let me know the user would also check the group. I attempted the group name as the same as the corpus username to see if it worked similar to merged groups. Mostly I tried the variations because the syntax for merged groups makes more sense to me. I'm still not quite sure what the reasoning (if any) there is behind the Global Group name. And the merged group syntax appears to allow for adding some users to the group where the Global Groups syntax only allows adding all users to the group. > >> When sending mail to a test user it does not appear to mark any mail as >> spam. Looking at the debug output there is also no indication that the >> corpususer tokens are being consulted. (I've included the debug outputs >> below) >> > The whole group evaluation is a mess! I need to fix that ASAP. > Any help would be greatly appreciated. Merged groups do appear to be doing an okay job but are less than ideal solution. I'll probably be working on doing a second check against the corpus user instead of using the merged group today since it'll allow me to implement the low confidence corpus check instead of always merging in the corpus data. Again thanks for taking a look at this, Ed -- Ed Szynaka Network/Systems Manager LocalNet Corp./CoreComm Internet Services ------------------------------------------------------------------------------ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
