At 16:24 2008-07-21 -0600, Steve Webb wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just switched our company over to Cyrus pop/imap recently and I've found
an issue where procmail is not detecting the "From" header properly and
even in the log file, procmail is getting confused.
Good, you have logs. So, how come you didn't post excerpts, along with
headers from a supoosedly misprocessed message, along with the recipe
which failed to "detect" the From header?
The headers from your email: :)
Return-Path: <cyrus(_at_)mail>
Great example of a poorly configured daemon, since it doesn't show the FQDN
of its host.
Received: from murder ([unix socket])
(authenticated user=swebb bits=0)
by mail (Cyrus v2.3.7-Invoca-RPM-2.3.7-1.1.el5) with LMTPA;
Mon, 21 Jul 2008 16:03:07 -0600
X-Sieve: CMU Sieve 2.3
FTR, headers INTERSPERSED with Received: headers has long generally been
considered a spammy trait.
[snip]
My procmail log:
[snip - a whole bunch of lines, with no reference to what is WRONG with them]
- From swebb Mon Jul 21 16:03:19 2008
Subject: Re: Cyrus and procmail
Folder: /var/spool/mail/swebb
(The "From swebb" (third line from the bottom) should be
From: PSE-L(_at_)mail(_dot_)professional(_dot_)org, yes)?
Actually, NO. The message YOU received came through the procmail list, so
the ENVELOPE From (the From without a colon) should be the sender, in the
case of this list:
From procmail-bounces(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE Mon Jul 21
15:25:05 2008
(example timestamp, not necessarily your message)
NOTE: This procmail log is being processed on my local machine. I fetch
mail from the server using fetchmail
AHA. Something you excluded from your original post. Fetchmail is very
likely causing the 'swebb' stuff to be inserted by your local MTA because
it's introducing the message to the MTA while running as user 'swebb'.
Fetchmail can be useful to consolodate mail from other places, but it is
still a mail kludge. Expect it to act much differently from mail that was
delivered via SMTP directly to your host.
which then goes through sendmail, then procmail. When I use procmail on
the server, the "From" line in the procmail logs shows "From
cyrus(_at_)mail(_dot_)cluster".
Er, so, the mail is arriving at some other machine, going through procmail
and being delivered to a cyrus IMAP/POP3 mailbox, and then you're
retrieiving it using fetchmail to your local machine and processing it
through your local MTA and LDA...
Forget the recipes, this is just the log file finding the wrong value for
the "From" header. My recipes all work great.
I'm unclear on what the PROBLEM is then. What are you saying doesn't
WORK? Or is it that you're taking offence to headers that OTHER PROCESSES
are generating?
Yea, procmail was working fine before the install of Cyrus, and these
procmail issues are popping up on other machines other than the mail
server - machines where no other software has been changed, email gets
forwarded to those machines and they are also having the same issue.
So, focus on the machine where changes took place.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail