From: "Roland Winkler" <winkler@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: mail splitting with mime-encoded headers
Date: Mon, 17 Jan 2022 11:54:43 -0600 [thread overview]
Message-ID: <87bl0as0ws.fsf@gnu.org> (raw)
In-Reply-To: <87leze20h9.fsf@tullinup.koldfront.dk>
On Mon, Jan 17 2022, Adam Sjøgren wrote:
> Roland writes:
>> What is the recommended way for dealing with mime-encoded headers when
>> splitting mail?
>
> I use this:
>
> ; Decode headers before splitting on them:
> (setq nnmail-mail-splitting-decodes t)
Thanks, that was exactly what I was looking for.
prev parent reply other threads:[~2022-01-17 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:47 Roland Winkler
2022-01-17 9:08 ` Adam Sjøgren
2022-01-17 17:54 ` Roland Winkler [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=87bl0as0ws.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=info-gnus-english@gnu.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).