Bug 89 - A_FROM_IN_AUTO_WLIST can't open auto_whitelist_path
Summary: A_FROM_IN_AUTO_WLIST can't open auto_whitelist_path
Status: RESOLVED LATER
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.0
Hardware: PC Linux
: P3 minor
Target Milestone: ---
Assignee: Craig Hughes
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-07 10:28 UTC by jdandrea
Modified: 2002-03-16 19:08 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jdandrea 2002-03-07 10:28:23 UTC 
Using SpamAssassin 2.01 on Linux with Exim (installed by ISP).

Mail recently started bouncing with message:

Failed to run A_FROM_IN_AUTO_WLIST SpamAssassin test, skipping:
        (Cannot open auto_whitelist_path
/home/johndoe/.spamassassin/auto-whitelist:
)

auto-whitelist file exists and is 600 perms. Changed to 700. No difference.
.spamassassin directory is 700 perms. Both appear consistent w/documentation
expectations.

One, then two .lock files seen in .spamassassin directory at time of bounce:

auto-whitelist.lock (created around 9:57am)
auto-whitelist.lock.localhost.fqdn.net.pid also present (localhost.fqdn.net 
being the FQDN of the localhost and pid most likely being the pid running the 
spam check at that moment). The latter file also had "localhost.fqdn.net.pid" 
within it multiple times - at least 25 times.

Deleted both lock files - no change.

To make matters more surreal, I have also learned that the mail _did_
bounce, yet the recipients claim to have still received the messages.
Not 100% sure if this is true or not (would need to compare headers
closely).

Disabled SpamAssassin in the meantime and filed report with ISP.
Advised I would be searching through spamassassin.org and bugzilla,
then posting to bugzilla worst case.

Clues welcome!
Comment 1 Craig Hughes 2002-03-08 11:12:18 UTC 
Subject: Re:  New: A_FROM_IN_AUTO_WLIST can't open
	auto_whitelist_path

What user owns the .spamassassin directory and its contents?
What user is spamd running as when trying to access the file?

Since the permissions are 0600 on the file, they'd have to be the same user.

If spamd is run with the "-D" flag, then it will produce debugging messages
which can help identify this.  Also, spamd logs through syslog details of
its processing which include (I think -- don't recall in 2.01) details of
the username being used to process each message.
Comment 2 jdandrea 2002-03-08 15:07:44 UTC 
Greetings!

The .spamassassin directory and contents are owned by user "foo" (say the 
email is foo@host.org). spamd ... well, that's a good question. I'd give you 
the answer to that but the ISP has recently deprecated SpamAssassin so now I'm 
suddenly unable to pursue this further! :-o

The permissions being 0600 - good point. The directory was 700 perms but the 
file was originally 664 perms. Perhaps SpamAssassin ran as a daemon and then 
didn't have permission to mess with the other files. And yet the whitelist 
file _did_ have content in it - if you were to do "strings" on it you'd get 
info. So something must have changed ...

I'll ask the ISP to please give this another shot with the -D flag. It also 
sounds like they need a newer release. :-)