At 04:14 PM 10/20/00 -0500, Jeff Howie wrote:
[snip]
HI all. I've been skulking for a bit, but still don't fully understand
what the problem is. I've got the following types of simple rules in my rc
file (here's but one example):
:0:
* ^TOcomp.os.linux.misc
comp.os.linux.misc
[snip]
Here's the headers from two separate messages, the first was properly
filtered by the above rule, the second stayed in my inbox. My mua
(mutt) showed the proper 'To: comp...' in the message header display
section for the good one, while the second (bad) shows only the actual
poster's 'From:' in the header.
Basically, what can I do to fix this?
GOOD:
====
[snip]
BAD:
====
From ddb(_at_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk Fri Oct 20 15:39:14 2000
Received: from localhost (jeffh(_at_)localhost [127.0.0.1])
by jeffh.federated.ca (8.9.3/8.9.3) with ESMTP id PAA11542
for <jeffh(_at_)localhost>; Fri, 20 Oct 2000 15:39:14 -0500
Date: Fri, 20 Oct 2000 15:39:14 -0500
From: ddb(_at_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk
Message-Id: <200010202039(_dot_)PAA11542(_at_)jeffh(_dot_)federated(_dot_)ca>
Received: from devaxp.federated.ca [172.28.11.126]
by localhost with POP3 (fetchmail-5.4.4)
for jeffh(_at_)localhost (single-drop); Fri, 20 Oct 2000 15:39:14 -0500
(CDT)
Path:
nntp1.deja.com!nnrp2.deja.com!nnrp2.deja.com!nntp2.deja.com!news.maxwell.syr.edu!colt.net!newspeer.clara.net!news.clara.net!newsfeed.icl.net!nntp.news.xara.net!xara.net!gxn.net!server6.netnews.ja.net!newsfeed.ed.ac.uk!news.cogsci.ed.ac.uk!excession!
Status: RO
Content-Length: 3306
Lines: 85
darren
From: ddb(_at_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk>Subject: Re: How can one app
crashing bring down whole system?
Date: Sat, 14 Oct 2000 14:08:23 +0100
Organization: University of Edinburgh
Lines: 37
Message-ID: <8s9ls8$jrp$1(_at_)pc-news(_dot_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk>
References:
<8s9jaf$iak$1(_at_)pc-news(_dot_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk>
<slrn8uglsg(_dot_)t6r(_dot_)cbbrowne(_at_)dantzig(_dot_)brownes(_dot_)org>
Reply-To: comp(_dot_)os(_dot_)linux(_dot_)misc(_at_)list(_dot_)deja(_dot_)com
NNTP-Posting-Host: dialup-2.cogsci.ed.ac.uk
X-Trace: pc-news.cogsci.ed.ac.uk 971528904 20345 129.215.144.22 (14 Oct 2000
13:08:24 GMT)
X-Complaints-To: usenet(_at_)cogsci(_dot_)ed(_dot_)ac(_dot_)uk
NNTP-Posting-Date: 14 Oct 2000 13:08:24 GMT
User-Agent: Pan/0.8.1beta6 (Unix)
X-No-Productlinks: Yes
Errors-To: errors(_at_)list(_dot_)deja(_dot_)com
To: comp(_dot_)os(_dot_)linux(_dot_)misc(_at_)list(_dot_)deja(_dot_)com
[snip]
The blank line after "Lines: 85" ends the header; the rest, which look like
former header lines, are now in the body (as far as mbox format is concerned).
Hence, mutt does not see the To: line in the "BAD" message since it's
after the blank line, so it shows the (first) From: line, which is before
the blank line.
I don't know how it might have got messed up; however, I speculate that it
may be related to that long Path: header present in the "BAD" message.
(I'm suspicious because it appears to have been truncated -- note that it
ends with a "!" -- , and the amount that came through is just under
256 characters.)
Hmmmm, I wonder, would $LINEBUF matter here? I don't think it should, but you
might try something like
LINEBUF=32000
at the top of your .procmailrc and see if you still get these.
HTH,
Stan
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail