http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5507
Summary: Unhelpful diagnostics when site rules directory is
inaccessible
Product: Spamassassin
Version: 3.2.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Libraries
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
I'm attaching a small patch to improve diagnostics when
site rules directory was present during install, but was
inaccessible to a process running SA.
It took us some running around in circles (on a mailing list)
when a user reported SA failing after a fresh install and
reporting
config: could not find site rules directory
even though the directory /usr/local/etc/mail/spamassassin
was present and accessible to anyone.
It turned out that one directory above, the /usr/local/etc/mail
was too strongly protected, and a sloppy -e() test in Perl
does not distinguish between 'does not exist' and 'is inaccessible'.
The attached patch turns a:
config: could not find site rules directory
into a:
config: path "/usr/local/etc/mail/spamassassin" is inaccessible:
Permission denied
config: could not find site rules directory
Please incorporate the patch to facilitate future troubleshooting.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
