-p works... mostly

[David Relson]

Hello Trevor,

bogofilter passthrough mode, i.e. "-p -e", is proven, reliable code
and has no known problems.

My mail server runs postfix and procmail.  For security I keep a copy
of each message before and after bogofilter processing.  With logging
enabled, this provides a record of each messages processing:

procmail: Opening "mail.backup"
procmail: Executing "bogofilter,-p,-l,-e,-u,-U"
procmail: Opening "relson"
procmail: Opening "spam-bogofilter"
procmail: Notified comsat:
"eric at 2127362:/var/spool/mail/spam-bogofilter"
>From erikajhenley_am at nic.frd.se  Wed Aug  4 17:14:17 2004
 Subject: We give you $200 bonus at Casino Zeal!
  Folder: spam-bogofilter                                1390

Using bogofilter's logging "-l" option also records each message in
/var/log/syslog.  The postfix/bogofilter combo provides this info:

Aug  4 17:14:17 nic postfix/cleanup[30492]: B06D0300A0:
message-id=<a2c101c47a68$bf15745f$0a0e72ee at cysnet.com.ar>
Aug  4 17:14:17 nic postfix/qmgr[19454]: B06D0300A0:
from=<erikajhenley_am at nic.frd.se>, size=1181, nrcpt=1 (queue active)
Aug  4 17:14:17 nic bogofilter[30509]: X-Bogosity: Spam,
spamicity=1.000000, version=0.92.4
Aug  4 17:14:17 nic postfix/local[30493]: B06D0300A0:
to=<eric at osagesoftware.com>, relay=local, delay=6, status=sent ...

I suggest that you turn on as much logging as possible with your mail
transfer, delivery, and user programs.  That will help significantly
in determining why some messages don't have their X-Bogosity lines.

HTH,

David