Bug 75814
| Summary: | spamassassin does not function | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Dumitru Ciobarcianu <cioby> |
| Component: | spamassassin | Assignee: | Chip Turner <cturner> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | tmus, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-02-28 22:07:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dumitru Ciobarcianu
2002-10-13 00:15:22 UTC
please attach the spam you're seeing trouble with. also please comfirm it works with the non-daemon spamassassin. an strace of the spamd daemon during this would also be helpful. This might actually be a problem with the spamassassin version included with Red Hat 8.0. I was investigatnig the same problem at my house last night and found that it was in the auto-whitelist functionality (-a passed to spamd) that the problem should be found... And the problem at my place is only there when spamc is run as root. For some reason the new_checker function in DBBasedAddrList.pm is seeing $path for the root user as //.spamassassin/ instead of /root/.spamassassin... try running "spamd -a -c" as root on one terminal (leave out the -d specified in the init.d script). Then on another tty run, also as root; "spamc </usr/share/doc/spamassassin-2.31/sample-spam.txt" and you will see: "Cannot create tmp lockfile //.spamassassin/auto-whitelist.lock : No such file or directory" This error is displayed from line 55 in DBBasedAddrList.pm. What i did to circumvent the error was to upgrade to latest RawHide 2.43-10 version, which does not seem to have this problem. I'm quite sure this issue was fixed a long time ago, and also RH8 has hit End Of Life support. You may want to upgrade to newer distributions anyway if you are still using RH8. File a new bug against the newer distributions if you are still having problems. Thank you. |