Re: How to troubleshoot new installation

Is anyone listening on this list? I see a couple of questions including mine have gone unanswered.
 



>________________________________
>From: Doug <[email protected]>
>To: "[email protected]" <[email protected]>
>Sent: Saturday, June 18, 2011 11:55 PM
>Subject: How to troubleshoot new installation
>
>I have been running Bogofilter for several years and really like it. It works very well.
>
>I brought up bogofilter on a new system -
>
>This is the new system - 
>
>slate:/usr/local/bin # bogofilter -V
>bogofilter-sqlite version 1.2.2
>    Database: SQLite 3.7.5
>Copyright (C) 2002-2010 David Relson, Matthias Andree
>Copyright (C) 2002-2004 Greg Louis
>Copyright (C) 2002-2003 Eric S. Raymond, Adrian Otto, Gyepi Sam
>
>And this is the old system, I am currently using -
>
>bogofilter-sqlite version 1.2.2
>    Database: SQLite 3.7.3
>Copyright (C) 2002-2010 David Relson, Matthias Andree
>Copyright (C) 2002-2004 Greg Louis
>Copyright (C) 2002-2003 Eric S. Raymond, Adrian Otto, Gyepi Sam
>
>I copied the database (wordlist.db) from the old system to the new. I am using the same procmail script. 
>
># filter mail through bogofilter, tagging it as Ham, Spam, or Unsure,
># and updating the wordlist
>
># :0fw: bogofilter.lock
># | /usr/local/bin/bogofilter -u -e -p -l -d /home/admin/.bogofilter
>
>
># if bogofilter failed, return the mail to the queue;
># the MTA will retry to deliver it later
># 75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
>
># :0e
># { EXITCODE=75 HOST }
>
>
># file the mail to spam-bogofilter if it's spam.
>
># :0:
># * ^X-Bogosity: Spam, tests=bogofilter
># IN.spam-bogofilter
>
># file the mail to unsure-bogofilter
># if it's neither ham nor spam.
>
># :0:
># * ^X-Bogosity: Unsure, tests=bogofilter
># IN.unsure-bogofilter
>
>All lines are commented out because of it failing. This is the same script that works fine on the original system.
>
>On the new system and with this script operational I get the 75 error on all emails and they go back to the queue and eventually die.
>
>They give this error message - 
>
>The original message was received at Mon, 13 Jun 2011 13:06:27 -0400
>from localhost [127.0.0.1]
>with id p5DH6PuD009336
>
>   ----- The following addresses had permanent fatal errors -----
>"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #admin"
>    (reason: Deferred)
>    (expanded from: admin)
>
>   ----- Transcript of session follows -----
>"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #admin"... Deferred: prog mailer (/bin/sh) exited with EX_TEMPFAIL
>Message could not be delivered for 5 days
>Message will be deleted from queue
>
>Bogoutil seems to work with the database fine - 
>
>slate:/usr/local/bin # bogoutil -H /home/admin/.bogofilter/wordlist.db
>Histogram
>score   count  pct  histogram
>0.00   320367 11.51 #######
>0.05     3138  0.11 #
>0.10     2899  0.10 #
>0.15     1198  0.04 #
>0.20     5535  0.20 #
>0.25     1740  0.06 #
>0.30     2901  0.10 #
>0.35     1528  0.05 #
>0.40     2347  0.08 #
>0.45     1531  0.05 #
>0.50     2328  0.08 #
>0.55     2112  0.08 #
>0.60     2513  0.09 #
>0.65     2485  0.09 #
>0.70     2538  0.09 #
>0.75     3088  0.11 #
>0.80     3580  0.13 #
>0.85     4422  0.16 #
>0.90     5399  0.19 #
>0.95  2412035 86.65 ################################################
>tot   2783684
>hapaxes:  ham  186718 ( 6.71%), spam 1829218 (65.71%)
>   pure:  ham  315835 (11.35%), spam 2406205 (86.44%)
>
>How can I check that bogofilter is working from the command line and determine exactly where my error is?
>
>
>Doug
>_______________________________________________
>Bogofilter mailing list
>[email protected]
>http://www.bogofilter.org/mailman/listinfo/bogofilter
>
>
>
_______________________________________________
Bogofilter mailing list
[email protected]
http://www.bogofilter.org/mailman/listinfo/bogofilter