Bug#293207: bogofilter: Any fix found?

[Matthias Andree]

"Dann Daggett" <dann at exposim.com> writes:

> Ok. However, I have no idea how to get a .procmailrc file to redirect
> output, so instead, I incorporated your printugid.c code (thanks for that
> btw) into my dmd_whitelist.c program and had it log the results in it's
> existing log file. It's output was:
>
> 03/07/05 17:40:43|ruid=500 euid=500 suid=500
> 03/07/05 17:40:43|rgid=500 egid=500 sgid=500
>
> On my system, 500 is both the passwd and group number associated to user
> 'dann'.
>
> I believe this proves that .procmailrc is being executed as user 'dann' does
> it not?

Yes, it does. That means I have no explanation currently what causes
root-owned log.* files to appear in your user's log file directory. The
rollover at 1 MB is what bogofilter requests, but the ownership is
bogus, as you stated. I'm stumped for now.

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

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