From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap-split-fancy broken
Date: Fri, 14 Mar 2003 18:00:56 +0100 [thread overview]
Message-ID: <iluwuj1opbr.fsf@latte.josefsson.org> (raw)
In-Reply-To: <uu1e6w903.fsf@axis.com> (Niklas Morberg's message of "Fri, 14 Mar 2003 11:14:04 +0100")
Niklas Morberg <niklas.morberg@axis.com> writes:
> There's something weird with nnimap-split-fancy, possibly
> due to the recent introduction of nnimap-split-download-body.
>
> The problem is that `to' now catches occurences in the body
> as well. Here's an example:
>
> (setq nnimap-split-rule 'nnimap-split-fancy
> nnimap-split-fancy
> '(|
> (to "ding" "lists/ding")))
>
> If a message is sent directly to me and contains `To: ding'
> in the body, the message will be split to lists/ding. This
> happens quite often since Outlook includes the original
> message with some headers when replying.
Hm, the code tries to narrow to headers. Could you M-x debug-on-entry
RET nnimap-split-fancy RET and look in the nnimap server buffer ("
*nnimap* SERVER") and check whether it is narrowed to the headers? If
so, try widening to see if it works.
> nnimap-split-download-body's value is default
I assume n-s-d-b-d's value was set to non-nil by spam.el.
next prev parent reply other threads:[~2003-03-14 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:14 Niklas Morberg
2003-03-14 17:00 ` Simon Josefsson [this message]
2003-03-17 12:10 ` Niklas Morberg
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=iluwuj1opbr.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).