Passthrough mode - X-Bogosity header & its effect on the corpus

[Stroller]

On Dec 1, 2003, at 9:13 pm, David Relson wrote:
>>
>> Excellent, thanks! Would anyone on the list have a maildrop recipe
>> which accepts the X-Bogosity headers & logs them..?
>>
>> I don't really want Bogofilter to do it's own logging, but prefer that
>> maildrop logs the bogosity along with the other headers it records.
>> I think this might be helpful in determining my own cutoff levels, but
>> I don't see how to get maildrop's log statement to record that line. I
>>
>> guess it might be possible if I parse this into a maildrop variable,
>> but I have no idea how to do that.
>
> Save all your spam and ham for tuning.  0.15.7 has a perl script that
> does the task, but it's rather slow.  0.15.8 and newer have a C version
> which is significantly faster and is still being tweaked.  Look for it
> in 0.15.10.

Hmmmn.... ok, fair enough. But maildrop already logs in this format:

...
------------------------------------------------------------- INBOX
Date: Tue Dec  2 19:00:08 2003
From: Graphics.design at graphicsdesign.com
Subj: Outsource Graphics Design? Creative and Effective Logo Design for 
your I
File: /home/stroller/.Maildir                                        
(5790)

----------------------------------------------- (User) Gentoo List
Date: Tue Dec  2 19:00:41 2003
From: "brett holcomb" <REMOVED at charter.net>
Subj: Re: [gentoo-user] KDE, Firebird, & Thunderbird
File: /home/stroller/.Maildir/.Geek.Linux.Gentoo Lists.User          
(2758)



It would be really nice to add the bogosity details to this log, but 
having Bogofilter output them directly won't cut it, as the "----- 
Spam" line will only be generated after maildrop has analysed the 
bogosity details, and the other headers are logged following that line.

If anyone knows how to do this, I'd be very grateful of any pointers,

Stroller.