Matt Kettler wrote on Wednesday, July 27, 2005:

>At 01:55 AM 7/27/2005, James Bucanek wrote:
>>I just upgraded my SA system and installed Razor.
>>
>>I have two e-mail addresses set up for spam and ham reporting. Both are 
>>sent to an mbox that is, twice an hour, shipped off to a script that runs 
>>sa-learn.
>>
>>When I installed Razor I modified the script to send the same messages to 
>>razor-report too.
>>
>>Later, I read that one shouldn't do that because it sends Razor the 
>>messages with the SpamAssassin headers. One should use 'spamassassin 
>>--report' instead.
>
>If your spamassassin markup is headers-only it's fine. Razor does NOT care 
>about headers at all.
>
>However, if you're using sa in a way that encapsulates spam, then you'll 
>want to use spamassassin --report.

No, I'm not encapsulating the spam. I've written some scripts which redirect 
the messages, unchanged, to the spam/ham reporting address.

So it look like I can just go back to using sa-learn and razor-report.

Thanks.

>
>>This is supposed to update the Bayes DB, strip the SA headers, and report 
>>it to Razor sans headers all with a single command. Apparently, I'm not 
>>doing it right.
>>
>>But when I run 'spamassassin --debug --report --mbox < queued_spam.mbox' I 
>>get a bunch of suspicious messages, which makes me think it isn't working 
>>right at all:
>
>Of course it isn't. spamassassin does not support --mbox, only sa-learn does.
>
>spamassassin only accepts single-message rfc-822 format.  

Then what does the --mbox switch do?

    twilightandbarking:~ james$ spamassassin --help
    SpamAssassin version 3.0.4
      running on Perl version 5.8.1
    
    For more information read the spamassassin man page.
    
    Usage:
        spamassassin [options] [ < *mailmessage* | *path* ... ]
    
        spamassassin -d [ < *mailmessage* | *path* ... ]
    
        spamassassin -r [ < *mailmessage* | *path* ... ]
    
        spamassassin -k [ < *mailmessage* | *path* ... ]
    
        spamassassin -W|-R [ < *mailmessage* | *path* ... ]
    
        Options:

<clip>  
         --mbox                            read in messages in mbox format
         --mbx                             read in messages in UW mbx format
<clip>
         -D, --debug [area=n,...]          Print debugging messages
         -V, --version                     Print version
         -h, --help                        Print usage message

-- 
James Bucanek <mailto:[EMAIL PROTECTED]>

Reply via email to