Bug 1093 - SQL / Local Configuration bug in 2.42
Summary: SQL / Local Configuration bug in 2.42
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 2.42
Hardware: PC Linux
: P2 normal
Target Milestone: 2.50
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-10 09:42 UTC by Kevin A. McGrail
Modified: 2002-12-27 01:53 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin A. McGrail 2002-10-10 09:42:50 UTC
Using v2.42 with the Mysql Preferences

If I put a whitelist_from *masa-inc.com in my localdb.cf, it seems to be
ignored.

If I put it in my SQL prefs, it works fine.

A roll-back to v2.41 confirmed that the entries in local configs and the SQL 
are additive.
Comment 1 Justin Mason 2002-10-14 06:31:58 UTC
what file exactly, and where in the filesystem?
I presume you mean /etc/mail/spamassassin/localdb.cf .
Comment 2 Kevin A. McGrail 2002-10-14 06:40:56 UTC
Your assumption and the location are correct.  Under 2.41, the localdb.cf is 
read and correctly parsed.  Under 2.42 and above I am getting erratic behavior*.

For example, I am now getting complaints that I have taken SpamAssassin away.  
The users in question have NO database settings and the spamassassin is 
reflected in the headers but not the subject lines.

Is it possible that if they have never configured any database settings, that 
somehow the defaults and the local cf's are not being used?  Have the defaults 
for SpamAssassin changed?  

*NOTE: The eratic behavior is caused by an upstream ISP running SpamAssassin 
through a milter.  I'm having trouble testing everything because of this.
Comment 3 Kevin A. McGrail 2002-10-14 09:31:51 UTC
As an FYI, I was reading through the Changes and stumbled on the @GLOBAL 
change.  I have added this functionality to the PHP-SA-KAM.  So perhaps this is 
a "temporary" fix as at least I know that there are "global" database 
configurations.
Comment 4 Duncan Findlay 2002-12-24 20:40:56 UTC
I don't understand what this is about... marking 2.50 cuz it sounds like we
should consider it for 2.50. Severity=normal cuz there seems to be a fix.
Comment 5 Justin Mason 2002-12-27 10:37:32 UTC
Kevin, I really can't see how this could be happening;
only thing I can think of is that the path SA expects
the local config files to be, is incorrect.

The local.cf files are read at spamd-start time.
Comment 6 Kevin A. McGrail 2002-12-27 10:53:09 UTC
Thanks for the follow-up again but we closed this as a non-bug some weeks ago.  
It was completely my stupidity in not knowing spamd needed to be restarted 
coupled with a over-awareness of problems because of the legit AWL problem I 
found.