Re: [dspam-users] SOLUTION: Postfix problem with global spam alias

On Mon, Nov 07, 2005 at 09:42:24AM -0500, Covington, Chris wrote:
> On Sat, Nov 05, 2005 at 01:12:38PM -0500, Andrew Boling wrote:
> > Myself, like a few others, have been experiencing a problem with the new
> > "global" spam user. This problem is characterized by dspam reporting an
> > error to the log that it does not recognize the signature you are
> > attempting to report. Apparently the command is unable to recognize
> > signatures unless when the --user is explicitly specified, contrary to
> > what the documentation is telling us.
> >
> > ...Or so us Postfix goobers think, anyway.
> >
> >
> > You're doing one of two things wrong.
> >
> > 1) You're running Postfix+dspam with dspam --daemon and still trying to
> > manually deliver your mail to the dspam command, you've misconfigured
> > your system. If you're using the dspam daemon as a content filter via
> > LMTP, you DO NOT need to configure the global spam alias inside the MTA
> > itself. If dspam.conf is properly configured, the daemon acting as a
> > content filter will parse out all incoming false positive/negative
> > reports before the MTA attempts to deliver them.
>
> I'm also experiencing this problem:
>
> ' failed11/07/2005 09:28:45] Signature retrieval for
> '1,436d5725196871232315631
> 29012: [11/07/2005 09:28:45] Unable to find a valid signature. Aborting.
> 29012: [11/07/2005 09:28:45] process_message returned error -5.
> dropping message.
>
> I have no way to train on errors (I see a lot of false positives,
> unfortunately, after my corpus feeding).
>
> However, if I have the signature inserted in the headers
> (signatureLocation=headers), how will dspam know what the signature is
> if a user simply forwards the email to an address? The way I intended
> to set it up was to have users drop false positives into an IMAP folder,
> then a perl script picks up the message (headers and all) and delivers
> it to a folder and runs dspam --user plusone --class=innocent
> --source=error --deliver=summary --process --stdout < ${FILE}.

OK, I've found a workaround for this. You can specify the signature by
the command line. So I've done this:

dspam --user plusone --source=error --signature=1,436d5725196871232315631 < ${FILE}

And I can train FPs / FNs now.

---
Chris Covington
IT
Plus One Health Management
75 Maiden Lane Suite 801
NY, NY 10038
646-312-6269
http://www.plusoneactive.com