From: "Roland Winkler" <winkler@gnu.org>
To: info-gnus-english@gnu.org
Subject: mail splitting with mime-encoded headers
Date: Sun, 16 Jan 2022 16:47:20 -0600 [thread overview]
Message-ID: <8735lnmh6v.fsf@gnu.org> (raw)
What is the recommended way for dealing with mime-encoded headers when
splitting mail? If I understand things correctly, Gnus looks at the raw
mails when splitting mail. So it may see mime-encoded headers (from:,
to:, subject:, etc.) which makes things like regexp-matching a less
straightfoward exercise. I may be missing something.
(Of course, it gets more expensive to split a large number of mail
messages if first lots of mime-encoded headers need to be decoded.
I guess that's the price one needs to pay for using mime encoding.)
Thanks,
Roland
next reply other threads:[~2022-01-16 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:47 Roland Winkler [this message]
2022-01-17 9:08 ` Adam Sjøgren
2022-01-17 17:54 ` Roland Winkler
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=8735lnmh6v.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).