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

[Stroller]

On Dec 1, 2003, at 12:29 pm, David Relson wrote:

> From your query it sounds like you might still be using 0.13.7.2.  If
> so, I'd suggest upgrading to the current stable release which is 
> 0.15.7.
>  It has lots of improvements, does a better job, and is faster....

Thanks!
There seems to have been a delay in getting 0.15.7 into my distro - 
apparently it depends upon xmlto. This may or may not be resolved, but 
I've nudged the maintainers at 
<http://bugs.gentoo.org/show_bug.cgi?id=31800>

> All that being said, bogofilter _does_ ignore the header "X-Bogosity:"
> line.  It sounds like something I should add to the FAQ :-)

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 to log 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.

Cheers,

Stroller.