This is what I think is happening. The incoming message was scanned by
dspam several times, once before it got to our internal mailing list,
and secondly after the mailing list sent it to me. Now it has 2 sets of
dspam headers.
X-DSPAM-Signature: 5367c3d722001198720193
...
X-DSPAM-Signature: 5367c3de22001657727144
Now when I retrain the message, and dspam should be looking for nn7144
in my account, instead dspam looks for nn0193 which is not in my account
(it is in the account for the mailing list). The log gets this:
May 5 13:02:59 hera dspam[2200]: Signature retrieval for
'5367c3d722001198720193' failed
We are using Postfix to pipe messages to dspam, and I will look at the
Postfix doco to help me configure it right, so dspam only sees messages
when they are going to a real user.
Another option would be that dspam could look at all the signatures, not
just the first one.
Another option is that dspam could know when it is scanning a message
destined for a mailing list, and not add headers at that time.
Thanks
Rick
Rick Leir, Senior Developer
http://CirrusComputing.com/
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
