On Sat, 2008-01-19 at 18:05 -0500, Paul Smith wrote:
> On Thu, 2008-01-17 at 15:23 -0430, Patrick O'Callaghan wrote:
[...]
> > I considered inserting a man-in-the-middle trap in /usr/bin/bogofilter
> > to log invocations but decided against it since I don't know if Evo
> > calls the actual BF executable or has a side entrance via a library
> > (so an empty log wouldn't tell me anything).
>
> >From the info you've provided, it seems like a man-in-the-middle trap is
> the next step. This was where I was ultimately headed when I sent my
> last email but I wanted to check some other things first; that's why I
> asked for people to enable logging, etc.
>
> I've looked at the source to the bogofilter plugin and it does indeed
> invoke /usr/bin/bogofilter with various arguments: there is no backend
> library (I don't think bogofilter provides one actually). Further, the
> plugin doesn't provide any customization whatsoever that would allow you
> to tell it to use a different program for man-in-the-middle operation.
> So, unfortunately, you'll have to replace your /usr/bin/bogofilter with
> the man-in-the-middle script.
>
> > When did you ask for this? I must have missed it. Any way here it is:
> > the wordlist.db has mod time of 2007-11-10 07:05, so I think it's safe
> > to say it's not being touched.
>
> My suspicion, then, is that the plugin is not even being invoked.
> However, please proceed with the man-in-the-middle approach and see what
> it tells you. You can probably guess what steps to take but enable
> logging/debug and write it to a test file. Also print the exit code
> from bogofilter to the test file, etc.
>
> You said something about Evo logging, but did you try to enable logging
> as I described before, by setting CAMEL_DEBUG=junk (make sure you export
> it) then starting evolution (from the shell command line of course)?
> Also be sure you run "evolution --force-shutdown" first and check that
> all evolution processes are dead before doing this.
I've inserted the man-in-the-middle trap and enabled CAMEL_DEBUG=junk.
The trap is as follows:
#!/bin/bash
# Man-in-the-middle trap for Bogofilter to log activity
# [EMAIL PROTECTED] 20/01/08
LOG=/tmp/BF_LOG
echo -n `date` >> $LOG
echo -n ':' >> $LOG
echo "$@" >> $LOG
/usr/bin/bogofilter.save "$@"
BF_STAT=$?
echo -n "Status " >> $LOG
echo $BF_STAT >> $LOG
exit $BF_STAT
(for the Unix-challenged: I moved the standard /usr/bin/bogofilter
to /use/bin/bogofilter.save and put this script in its place, chmoded to
executable of course. It just logs the arguments to any calls with a
timestamp and exit status, and passes through the call to the real
executable).
After a day of use the log file is empty. The debug output from Evo
shows no activity related to junk filtering. I think it's safe to say
that the junk filter (BF) is never being called. In fact it isn't even
being called when explicitly invoked to learn junk via the Junk toolbar
icon.
> If you do this you SHOULD see debug output for the bogofilter junk
> plugin for EVERY email you receive.
Again, nothing, nada, zip, zilch, ...
> It's possible, though, that your version of Evo was not built with
> proper debugging enabled; in that case you might not see it. I don't
> know that much about Fedora, since I gave up on Red Hat back around Red
> Hat 5 or 6 or so, but maybe they have debug build packages you could
> install instead?
None that I can find, but I haven't looked very hard. I'll consider
recompiling from source, but note that the first time I saw this problem
it was from a self-compiled version, so it may have nothing to do with
the Fedora package as such.
poc
_______________________________________________
Evolution-list mailing list
Evolution-list@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-list
