From: kai@emptydomain.de (Kai Großjohann)
Subject: Need to MIME-process a message after decrypting
Date: Fri, 22 Jul 2005 16:17:26 +0200 [thread overview]
Message-ID: <m2u0inhqmh.fsf@emptydomain.de> (raw)
I have access to a mail server that supports "autopgp". This is a
feature where you put the string "autopgp" into the subject line and
the mail server automatically encrypts the mail to all recipients.
(This only works for recipients on the same server, obviously.)
An autopgp message arrives as a somewhat strange format. Here is what
I get in the article buffer after entering my passphrase:
From: kai.grossjohann@dieneueepoche.com (Kai Großjohann)
Subject: test autopgp
To: Kai Großjohann <kai.grossjohann@dieneueepoche.com>
Date: Fri, 22 Jul 2005 14:02:28 +0200
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Sch=F6ne Umlaute.
As you can see, the encrypted bit contains MIME headers. How do I get
Gnus to look for and interpret these headers prior to displaying the
message?
Below, please find an excerpt of the message (sans some headers and
with the actual encrypted bits replaced by "x").
tia,
Kai
X-From-Line: imap Fri Jul 22 14:02:41 2005
To: Kai =?iso-8859-15?Q?Gro=DFjohann?= <kai.grossjohann@dieneueepoche.com>
Subject: test autopgp
Date: Fri, 22 Jul 2005 14:02:28 +0200
X-Gnus-Mail-Source: imap:mail.dieneueepoche.com:INBOX
Message-ID: <m2y87zhwvf.fsf@dieneueepoche.com>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (darwin)
X-MIMEGPG-Plain: version 1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Lines: 22
-----BEGIN PGP MESSAGE-----
xXxXXxXxxXXxXxxxXXxxXxxxXXxxxxxXXxxXXXxXXXXxXxxxXxxxxXXxxXxXxxXx
xxxXxXXXxxxXXXXXxxxxXXXxxxxXxXxXXxXxXXXxxXxXXxxxxxXxxxxXxXxxxXxX
xXxXXXXxxXxxXXxxxxXxxxxxxXXXxxXxxxXxXxxxxxXXXXXxxxXXXxxXxXxxXxxx
xxXXxxxxxXxXxxXxXxXxXxxxxxXxxxxXXxxxxxxxXxxXXxxxxXxxXXxXxxxxxXXX
xXxxxxxxxxxxXXxXXXXxxxXxXXXXXXxxXxxxxxxxxxXxxXXxxXxXxXxXxxxxxxXx
XxxxXXXXXxxxXxXXxXxXxxxxxXxxxxxXxXxxXxxXxXxxXxxxXxxxxXXXxxxXxxxx
XxxxxXxxxXxXxxXxxXxXxXxXXxxXxxxxXXXxxxXxxxxxXXxxxxXxxXXxXxXxxxXx
xXxxxxxxXxxXXXxxxXxXXXxxxXxxxxxXxxxxxxxXXxxxxxxxxXxxxxxXXXXxxXXx
xXxXXXxxxxxxxXXxxxXxXXxxXXXxXXxxxxxxxXXXXxxXXxXxxXxxxxXxXXXXxxxx
XXXxXXxxxXxxxxxxxxXxxXxxxxxxxxXxxXXxXxxXxxXxxXxxXXXxXXXXxxXxxxXx
xXXXxxxxXxxxxXxxxXxXXxxxXxXxxXxxxxxXxXxxXxxxxxXxxxXxXxxxXXxxxXXX
XxXXXXxxXXxxxXXXXXxxXxXXxxXXXxXXxxXxXxxxxxXXxxxxxXxXxXxxXXxXxXxx
xxXxxXxxXXxXXxXxXxxXxxxxxxxxxXxxXxXXxxxxXxXXXxXxXxxXXxxxXXxxxXXx
XxxxXXxxXXxxxxxxXxxXxXxxxxxXXxXXxXxxXxXxxxxXXxxXxxxXXXXXxXxXxxxx
XxxxXxxxXXxx
xXXxx
-----END PGP MESSAGE-----
next reply other threads:[~2005-07-22 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 14:17 Kai Großjohann [this message]
2006-04-14 7:10 ` Lars Magne Ingebrigtsen
2006-04-18 8:49 ` Simon Josefsson
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=m2u0inhqmh.fsf@emptydomain.de \
--to=kai@emptydomain.de \
/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).