From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] encoded from/subject lines?
Date: Wed, 13 Jun 2007 14:38:04 -0700 [thread overview]
Message-ID: <1181770524-sup-1225@south> (raw)
In-Reply-To: <1181763799-sup-5238@zap>
Excerpts from Ian Taylor's message of Wed Jun 13 12:47:56 -0700 2007:
> Now, a lot of these messages also seem to have portions of the from and
> subject lines that look like this:
>
> - From: =?ISO-8859-1?B?QW1hem9uLmNvbQ==?= <books at amazon.com>
These are RFC 2047 headers. Decoding them is on the todo list. If this
is prevalent, I will bump up the priority.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-06-13 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 19:47 Ian Taylor
2007-06-13 21:38 ` William Morgan [this message]
2007-06-14 0:15 ` jeff covey
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=1181770524-sup-1225@south \
--to=wmorgan-sup@masanjin.net \
/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