Elias Oltmanns <[EMAIL PROTECTED]> wrote: > Richard Freeman <[EMAIL PROTECTED]> wrote: >> Elias Oltmanns wrote: >>> >>> 1. Specify the actual user instead of root on the commandline. >>> >> >> Message successfully retrained >> >>> 2. Execute >>> # /usr/bin/dspam --source=error --class=spam --user root >>> --signature=1000,47601b27117601804284693 >>> >> >> Message successfully retrained >> >> >>> 3. The same with user instead of root. >> >> Message successfully retrained >> >>> >>> 4. Add --mode=TEFT to the commandline options. >> >> When used with the failing commandline (--user=root, message content >> piped in) it still doesn't work. > > This strikes me as distinctly odd. I can't help but think that a bug > somewhere in the code scanning messages for signatures may be the cause > of your troubles.
Or another pitfall in the configuration, after all. It has just occurred to me that the preference for the signature location might play a role in it. Assuming that your default preference is to put the signature in the body but some of your users prefer their signature in the headers. Unless you have changed the preference for root to put signatures into the headers, dspam will probably only scan the body of incoming messages for a signature. Could you make sure that the root has signatureLocation set to headers and try again? I know for sure that dspam searches headers *and* the body for a signature if signatureLocation is set to headers, but I haven't checked what happens if it is set to body. Hope that helps, Elias
