Bug 79608
Summary: | procmail runs but does not correctly apply rules | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Graham Freeman <graham> | ||||||
Component: | spamassassin | Assignee: | Chip Turner <cturner> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 8.0 | CC: | cturner, email1, wtogami | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i686 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2004-02-28 22:13:56 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: | |||||||||
Attachments: |
|
Description
Graham Freeman
2002-12-13 22:46:58 UTC
Created attachment 88710 [details]
Output of Sean B. Straw's "procdiag.sh" script
Created attachment 88711 [details]
List of RPMs on the system in question
Also, my RH7.3->RH8.0 transition was done by creating a new RH8.0 system from scratch. In other words, I didn't attempt a foolhardy upgrade process. The original RH7.3 system in question is still up and running, with a modified workload. I'm having the same problem. Is there any fix or work around? Thanks to helpful advice from Alessandro Forghieri from 'orion.it', I've been able to narrow down the source of the problem to the Red Hat 'spamassassin-2.31-16' RPM package. Removing the following two lines from my .procmailrc caused every other rule in my .procmailrc to start working again: :0fw | /usr/bin/spamassassin Mr. Forghieri said that his problem went away when he upgraded to a newer version of SpamAssassin. I haven't done that yet because I'd prefer to stay with the Red Hat RPMs, since that's what I pay $60/year/system for. I finally figured out a usable .procmailrc, thanks in part to Peregrine Hardware's installation notes - in particular the file at http://www.peregrinehw.com/downloads/SpamAssassin/INSTALL. Here's my functional procmailrc file: [...begin quote of functional .procmailrc...] SHELL=/bin/sh LOGFILE=logs/procmail VERBOSE=yes LOGABSTRACT=all :0c: mail-backup :0ic # Keep a backup of each of the last 128 messages received | cd mail-backup && /bin/rm -f dummy `/bin/ls -t msg.* | /bin/sed -e 1,128d` :0fw # Don't process anything over 256K - most spam is smaller than this, # and we have limited system resources. * < 256000 | /usr/bin/spamc -f :0e { EXITCODE=$? } :0: * ^X-Spam-Flag: YES mail/spam :0: * ^TO_rt-users@lists\.fsck\.com mail/rt-users :0: * ^TO_outlook-users@yahoogroups\.com mail/outlook-users :0: * ^TO_procmail@Lists\.RWTH-Aachen\.DE mail/procmail-list :0: * ^TO_openldap-software@OpenLDAP\.org mail/openldap-software :0: * ^TO_amanda-users@amanda\.org mail/amanda-users :0: * ^TO_achievo@achievo\.org mail/achievo :0: * ^TO_IMAP.edu mail/imap :0: * ^TO_imap.edu mail/imap [...end quote of functional .procmailrc...] So is there still a problem with our procmail/spamassassin? Yes, in that the procmail-based invokation of SpamAssassin that works on Red Hat 7.3 and is referenced in the SpamAssassin documentation doesn't work on Red Hat 8.0. Not only doesn't it work, but the procmail logs are baffling and bordering on misleading. It's probably not a RedHat-initiated problem, but if Mr. Forghieri is correct that upgrading to a newer version of SpamAssassin fixes things, then I'd say that Red Hat should either issue an updated spamassassin RPM or fix the documentation at line 116 in /usr/share/doc/spamassassin-2.31/README Do you have any comments on this, Chip? you can try the spamassassin from rawhide; it is a more recent version. I'd also suggest trying the perl from rawhide as well, but you may need to build it via src rpm. this bug doesn't affect everyone, though, so it has yet to be determined how urgent an errata is. we'll take this into account but chances it won't be for a while, so your best bet is to try rawhide. Thanks for the suggestion, but since I found a usable .procmailrc entry for RH 8.0's current spamassassin, I'll just leave it as-is. I try to keep my RH machines as vanilla as possible so that I can just ride the RH-issued upgrade cycle. I suspect, however, that there are more than a few people who're having the same problem as me but just aren't reporting it. Evidence of others having the same problem but not reporting it: Mr. Klicka from the domain "netpro.cz" contacted me privately and said that he was having the same problem. I gave him my .procmailrc as a workaround. I also had this problem on a .procmailrc that I'd brought over from Debian's Woody release - worked fine under Woody, failed under RH8. I was able to get spamassassin to work with procmail under RH 8 by modifying the normal spammassassin recipe as described in the docs: :0fw: spamassassin.lock * < 256000 | spamassassin to this: :0fw: spamassassin.lock * < 256000 | spamassassin --pipe I think what's going on is that spamassassin (at least the version shipped with RH 8) by default writes the message to the mail spool after processing, unlike spamc which defaults to writing the message to stdout. Apparently procmail doesn't intercept the message on the way to the mail spool, so the message bypasses the rest of the procmail filters. The "--pipe" command tells spamassassin to send its output to stdout instead, which procmail can grab and continue processing. RH8 is no longer a supported product, and I highly suspect that this problem is solved in newer distributions. Please open a new bug if you still have problems like this in newer distributions. Thank you. |