You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2010/01/12 05:36:45 UTC
[Bug 6283] New: /var/lib/spamassassin/3.003000/ exists but empty
causes failure
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
Summary: /var/lib/spamassassin/3.003000/ exists but empty
causes failure
Product: Spamassassin
Version: 3.3.0
Platform: Other
OS/Version: All
Status: NEW
Severity: minor
Priority: P5
Component: spamc/spamd
AssignedTo: dev@spamassassin.apache.org
ReportedBy: wtogami@redhat.com
My RPM package unpacks the rules into /usr/share/spamassassin/ so spamassassin
will work before the first sa-update.
During debug testing I wiped out the contents of
/var/lib/spamassassin/3.003000/ then restarted spamd. To my surprise spamd and
spamassassin fail because it is ignoring the rules in /usr/share/spamassassin
expecting to find rules in /var/lib/spamassassin/3.003000/. I had to delete
the empty directory in order for it to behave as expected.
Perhaps we should ignore the packaged rules only if
/var/lib/spamassassin/3.003000/updates_spamassassin_org/ is missing? This will
reduce the chance of someone being confused by this behavior in the future.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6283] /var/lib/spamassassin/3.003000/ exists but empty causes
failure
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
--- Comment #2 from Warren Togami <wt...@redhat.com> 2010-01-11 22:00:43 UTC ---
Any other suggestion to make this failure less confusing then?
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6283] /var/lib/spamassassin/3.003000/ exists but empty causes
failure
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
--- Comment #3 from Daryl C. W. O'Shea <sp...@dostech.ca> 2010-01-11 22:33:58 UTC ---
Other than "don't do that", I can't think of any. I don't think it's been a
commonly reported issue.
The behaviour is described in the documentation:
perldoc spamassassin
=====
CONFIGURATION FILES
The SpamAssassin rule base, text templates, and rule description text
are loaded from configuration files.
Default configuration data is loaded from the first existing directory
in:
/var/lib/spamassassin/3.002000
/usr/local/share/spamassassin
/usr/local/share/spamassassin
/usr/local/share/spamassassin
/usr/share/spamassassin
=====
/var/lib/spamassassin/3.002000 exists so that's where we load config. I'd say
you could debug about it, but then if they're running with debug enabled they
can see where the rules are being loaded from anyway. It may just come down to
if you want your config loaded don't delete it.
Of course, I may be open to something like "if the .../3.002000/ directory is
empty don't use it". That only disallows the case where somebody wanted to
load all of their config from a user prefs file (I'm not sure that would even
be possible or work anymore).
I admit that I'm not a fan of mucking with this code before a release though.
I'd hate to introduce something that isn't portable.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6283] /var/lib/spamassassin/3.003000/ exists but empty causes
failure
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
Daryl C. W. O'Shea <sp...@dostech.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spamassassin@dostech.ca
--- Comment #1 from Daryl C. W. O'Shea <sp...@dostech.ca> 2010-01-11 21:59:46 UTC ---
-5. No. :)
There is no requirement to use the updates.spamassassin.org channel rules.
This is by design so that you can use your own rulesets entirely.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 6283] /var/lib/spamassassin/3.003000/ exists but empty causes
failure
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6283
Karsten Bräckelmann <gu...@rudersport.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #4 from Karsten Bräckelmann <gu...@rudersport.de> 2010-03-03 20:55:01 UTC ---
Agreed, this works exactly as intended and documented. Closing Resolved
WONTFIX.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.