Hi,
I have been using spamassassin for some time alongside procmail (3.22-9),
postfix (2.1.1-3.MySQL.sasl2.tls.rh9) and mysql (4.0.20-0). I was running
2.63 until last week and all was fine and very stable until I upgraded to
2.64, when for some reason SQL options were being ignored.
Procmail passes the mail like this:
:0fw
# Only scan messages under 150k to reduce load
* < 150000
| spamc -f -u $USER
I have checked spamd is being passed the same options as before the upgrade:
-d -c -a -q -x -u postfixfilter
and have run spamd in debug mode:
-D -c -a -q -x -u postfixfilter
That is where it becomes odd - it works (i.e. retrieves SQL prefs) when in
debug mode but not when daemonised! The only change is from -d to -D...
My spamd messages in /var/log/maillog looks like this when run with -d:
Sep 11 13:49:39 mail-1 spamd[20295]: connection from
mail-1.freshmessaging.com [127.0.0.1] at port 44654
Sep 11 13:49:39 mail-1 spamd[20435]: handle_user: unable to find
user 'andy'!
Sep 11 13:49:39 mail-1 spamd[20435]: Still running as root: user not
specified with -u, not found, or set to root. Fall back to nobody.
Sep 11 13:49:39 mail-1 spamd[20435]: processing message
<[EMAIL PROTECTED]> for andy:99.
Sep 11 13:49:42 mail-1 spamd[20435]: clean message (0.2/5.0) for
andy:99 in 3.1 seconds, 1447 bytes.
(I know it is not fetching SQL prefs, as no query reaches MySQL, and
my prefs score should be 4, not 5)
My current assumption is that the second and third line is the problem, but
why would this result from an upgrade? Obviously - I *have* specified the
user with -u - why is this being ignored? User postfixfilter has always
existed.
Any ideas, or further investigation needed?
Thanks in advance,
Andy
