Fwd: SQLite and postfix...

[Glenn Steen]

On 01/02/06, Julian Field <MailScanner at ecs.soton.ac.uk> wrote:
> Glenn Steen wrote:
> > ---------- Forwarded message ----------
> > From: Glenn Steen <glenn.steen at gmail.com>
> > Date: 01-Feb-2006 18:23
> > Subject: SQLite and postfix...
> > To: MailScanner at lists.mailscanner.info
> >
> >
> > Just a note, if this hasn't been covered already:
> >
> > Updated to the latest stable (4.50.14) on my prod machine running
> > postfix...It's a Mdv 10.2, so I used that rpm method.
> >
> > Apparantly the SQLite db got created during install, with only user rw
> > perms... and a "non-postfix" user. This made MailScanner loop during
> > startup (all the children died immediately). Running --debug
> > complained about line 172 in SA.pm, which happen to be an operation on
> > the SQLite, so ... eventually led me right:-).
> >
> > Simple fix is to remove the file
> > /var/spool/MailScanner/incoming/SpamAssassin.cache.db and do "service
> > MailScanner restart" ... and a pristine file with the correect
> > perms/owner get created. One could've just changed the owner, of
> > course:-).
> >
> > Other than that, it looks to be _really_ nice... and fast.
> The db file shouldn't be created by the installation. Are you sure you
> didn't run it at all before setting the Run As User?

Yeah, pretty sure. It was an upgrade, not an install... So MailScanner
was already set for the postfix user, and yes... I did do the
suggested upgrade of conf file (and triple checked with diff and
reading the file from top to bottom and --linting) before restarting
the MailScanner service and putting in the first message (via
telnet)... Immediately noted a few <defunct> processes, and the
message just sat there... So I don't think it was anything like that.
I'll probably get to redo the upgrade tomorrow (on the other server),
and will be sure to take better notes then.
Come to think of it, I might have done a "MailScanner --lint" before
upgrading the MailScanner.conf file... It complained about the
spurious spam.assassin.prefs.conf line, IIRC... But it should still
have switched into "postfix" user, right? Or did that prevent it from
using it, then perform the spam cache query ... which then created the
bum file?
I'll try retrace my steps tomorrow and see what gives.

Cheers
--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se