From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: Fancy splitting getting headers from included text
Date: Mon, 14 Apr 2003 11:53:20 -0400 [thread overview]
Message-ID: <874r51jcsv.fsf@cag.lcs.mit.edu> (raw)
In-Reply-To: <ilur88pcb0p.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sun, 30 Mar 2003 14:08:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Simon Josefsson <jas@extundo.com> writes:
> I think it was reported to happen for nnmail too. Hm. Those who are
> seeing this, are you using spam.el and downloading bodies too?
Using spam.el, yes. Relevant parts of my .gnus file:
(setq nnmail-split-fancy
'(|
(: spam-split)
(to "reuse-\\(\\w*\\)@mit\\.edu" "mail.lists.reuse.\\1")
(any "dmaze@.*mit\\.edu" "mail.misc.personal")
"mail.misc.impersonal"))
(setq nnmail-split-methods 'nnmail-split-fancy)
(setq mail-sources '((imap :server "po10.mit.edu" :password ""
:stream kerberos4 :authentication kerberos4
:predicate "UNDELETED")))
(setq spam-split-group "mail.misc.spam")
Given this set of rules, the attached message trips the bug: it got
sorted into mail.lists.reuse.ask, where reuse-ask is only mentioned in
the body of the message. It should go in mail.lists.reuse.housing,
since that's what's in the headers.
[-- Attachment #2: reuse-misfiled --]
[-- Type: message/rfc822, Size: 2047 bytes --]
From: <reuse-request@MIT.EDU>
To: <reuse-housing@mit.edu>
Subject: apartment wanted (fwd)
Date: Mon, 14 Apr 2003 11:36:20 -0400 (EDT)
Message-ID: <Pine.GSO.4.33L.0304141136170.9597-100000@scrubbing-bubbles.mit.edu>
---------- Forwarded message ----------
Date: Mon, 14 Apr 2003 11:31:20 -0400
From: Laura Redi <redi@MIT.EDU>
To: reuse-ask@mit.edu
Subject: apartment wanted
Hi,
I'm looking for a studio or 1 BR apartment available June 1 or possibly
earlier. If you know of anyone who plans to be moving out of his/her
place please let me know.
Thanks,
Laura
--
Laura Redi
Ph.D. Candidate
Speech and Hearing Bioscience and Technology
Harvard-MIT Health Sciences Technology Program
redi@mit.edu
www.mit.edu/~redi
W: 617-253-5957
[-- Attachment #3: Type: text/plain, Size: 423 bytes --]
> Could you edebug nnmail-article-group to see if nnmail-split-fancy
> is somehow invoked without narrowed headers?
It doesn't get tripped if I 'B q' having started Gnus, only while mail
is being slurped in. This makes it a little harder to debug. :-/
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next prev parent reply other threads:[~2003-04-14 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 19:02 David Z Maze
2003-03-26 8:21 ` Niklas Morberg
2003-03-30 2:47 ` Lars Magne Ingebrigtsen
2003-03-30 9:31 ` Kai Großjohann
2003-03-30 12:08 ` Simon Josefsson
2003-04-05 13:29 ` Ted Zlatanov
2003-04-14 15:53 ` David Z Maze [this message]
2003-04-14 16:33 ` Simon Josefsson
2003-04-14 20:25 ` David Z Maze
2003-04-15 17:44 ` Ted Zlatanov
2003-04-15 18:12 ` David Z Maze
2003-04-15 19:47 ` Ted Zlatanov
2003-05-07 14:27 ` Niklas Morberg
2003-06-11 9:23 ` Niklas Morberg
2003-06-13 8:33 ` Niklas Morberg
2003-06-13 9:35 ` Niklas Morberg
2003-06-13 9:50 ` [PATCH] " Niklas Morberg
2003-06-13 21:07 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874r51jcsv.fsf@cag.lcs.mit.edu \
--to=dmaze@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).