Bug#293207: bogofilter: Any fix found?

[David Relson]

On Mon, 7 Mar 2005 18:57:28 -0800
Dann Daggett wrote:

> >> Finally, I'm still not clear exactly which program is creating new 
> >> log.0000000 files in ~/.bogofilter when the current log file reaches 
> >> 1MB. Is that the Berkley DB program or bogofilter doing that?
> >
> >bogofilter links against the Berkeley DB library, so Berkeley DB does
> >everything on behalf and account of bogofilter. This means, unless
> >there were a serious kernel bug, some root process must also be
> >running bogofilter because your .procmailrc* bogofilter cannot possibly
> >cause root-owned files to be generated, Linux doesn't support file
> >giveaways in default settings either.
> >
> >Do you have any system-wide cron jobs? Check /etc/cron*,
> /var/spool/cron/tabs.
> 
> Aha! I think you've found it.
> 
> I have a cron job that's probably the culprit.
> 0-59 * * * * /usr/local/bin/dmd_todo
> 
> This is my own C program that processes spam training feedback that come
> back in from the user (i.e. dann) and executes bogofilter to update the
> wordlist accordingly. It uses a system() call sending the following command:
> 
> 	/usr/local/bin/bogofilter -s
> 		 -d "/home/dann/.bogofilter"
> 		 -I "/home/dann/Procmail/103"
>    
> I set this as a root cron job since it processes many different users spam
> training. I am now assuming that if this program's execution of bogofilter
> causes the log file to reach 1MB, the new log file created is owned by root!
> 
> If this is the case I need to include a bogofilter option so it executes as
> the actual user being updated. I found no such option in the man pages
> however.
> 
> If there is no such bogofilter option, perhaps I should not have this
> dmd_todo program run from root's cron, but create a cron job for every user
> to run it (but re-code the program to process only one user instead of all
> of them).
> 
> Or, perhaps you have a better suggestion?
> 
> Thank you so much!
> Dann

Hi Dann,

Bogofilter has no "change uid" capabilities.  Procmail, maildrop, etc
already handle that well enough.

Why not run the cron job as "dann"??  Likely all you need to do is
create /etc/cron.d/dann with the "0-59 * * * * ..." line.  By the way,
if you really want to run it every minute, using "* * * * * ..." will
work.  Alternatively, run it hourly and lessen the load on the mail
server.

Regards,

David



_______________________________________________
Bogofilter mailing list
Bogofilter at bogofilter.org
http://www.bogofilter.org/mailman/listinfo/bogofilter