From: Vadim Gutnik <gutnik@mit.edu>
To: ding@gnus.org
Subject: Re: nnimap, MIME, and split-fancy
Date: Tue, 08 Jan 2008 15:43:02 -0500 [thread overview]
Message-ID: <rro4pdof3qh.fsf@vinegar-pot.mit.edu> (raw)
In-Reply-To: <v98x34q79k.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat\, 05 Jan 2008 22\:42\:15 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Thu, Nov 15 2007, Vadim Gutnik wrote:
>
>> I'm using No Gnus 0.6, and nnimap.
>>
>> I get some mail with Subject lines that look like this:
>>
>> Subject:=?iso-8859-1?B?UXVhcmFudGluZSBTdW1tYXJ5IDExLzE1LzIwMDcgMTI6MDAgcG0=?=
>>
>> gnus graciously decodes that, to look like this:
>>
>> Subject: Quarantine Summary 11/15/2007 12:00 pm
>>
>> But I can't split on the decoded subject line with nnimap.
>> The relevant part of my .gnus is:
>>
>> (setq nnmail-mail-splitting-decodes 't)
>> (setq nnmail-split-methods 'nnmail-split-fancy)
>> (setq nnimap-split-rule 'nnmail-split-fancy)
>> (setq nnimap-split-inbox '("INBOX"))
>> (setq nnmail-split-fancy
>> '(| (from mail "INBOX/mailbounce")
>> ("subject" "Quarantine" "INBOX/trash")
>> "INBOX/unsorted"
>> )
>> )
>>
>> With this setup, "B q" tells me the mail would get sorted to
>> INBOX/trash, presumably because nnmail is interepreting the split rule,
>> and with (setq nnmail-mail-splitting-decodes 't), it parses the
>> MIME. But the automatic respooling, or respoolig if I explicitly try
>> "B r nnimap" sends it to INBOX/unsorted.
>>
>> Am I making some configuration mistake, or is this a bug?
>
> Does adding`gnus-article-decode-encoded-words' to `nnmail-split-hook'
> work fro IMAP splitting? If not, maybe it could be added?
I added the line
(add-hook 'nnmail-split-hook 'gnus-article-decode-encoded-words)
I don't see the behavior change; it still doesn't work correctly.
Vadim
prev parent reply other threads:[~2008-01-08 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rrok5ojktjf.fsf@vinegar-pot.mit.edu>
2008-01-05 21:42 ` Reiner Steib
2008-01-08 20:43 ` Vadim Gutnik [this message]
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=rro4pdof3qh.fsf@vinegar-pot.mit.edu \
--to=gutnik@mit.edu \
--cc=ding@gnus.org \
/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).