Bug#3042: Elm produces bogus Content-Type header for PGP signed stuff (was Re: pine doesn't handle pgp signed messages (was Re: New uploads))
Package: elm
Version: 2.4pl25-2
See the messages below. Basically, Elm should not tag these messages
with a content-type which implies that they're unreadable.
Ian.
Michael Meskes writes ("Re: pine doesn't handle pgp signed messages (was Re: New uploads)"):
> Ian Jackson writes:
> > This is not a bug in Pine (wow!) It's a bug in whatever program
> > Michael Meskes is using to generate is messages. They say, in the
> > headers:
> > Content-Type: application/X-pgp-message
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: 7bit
>
> I use elm and sign with hitting p and s in the menu.
>
> Package: elm
> Status: install ok installed
> Priority: standard
> Section: mail
> Maintainer: Carl Streeter <streeter@cae.wisc.edu>
> Version: 2.4pl25-2
> Provides: mail-reader
> Depends: mail-transport-agent, ncurses3.0, libc5
> Suggests: metamail, pgp
> Description: A full screen ELectronic Mail interactive user agent.
> Elm is a mail user agent (MUA) for Debian.
> .
> An MUA is the visible part of the mail system - It interacts with
> the user to display, store, create and send mail.
> .
> Other MUAs may may be used on the same system as elm without
> causing problems.
> .
> In order to make use of elm you must have a single mail transport
> agent such as smail or sendmail installed. If you wish to send
> messages other than just to other users of your system you must
> also have appropriate networking support in the form of IP or uucp.
> .
> This version of Elm also has patches to allow it to work more
> comfortably with PGP (Pretty Good Privacy), a program to keep
> prying eyes where they don't belong.
>
>
> Package: pgp-i
> Status: install ok installed
> Priority: extra
> Section: non-free
> Maintainer: Ian Jackson <iwj10@cus.cam.ac.uk>
> Version: 2.6.2i-5
> Provides: pgp
> Depends: libc5
> Conffiles:
> /etc/pgp-i.conf cd5985f8a34070fdc9c1877b33343325
> Description: Public key encryption system (International version)
> Pretty Good Privacy is general-purpose public key encryption
> system written by Philip Zimmerman. It is often used in email
> conversations where confidentiality and integrity are important.
> .
> It is VERY IMPORTANT that you read the documentation (installed
> in /usr/doc/pgp) before attempting to use PGP. If you do not
> do so you will probably lose any security you might gain from
> PGP, and not even realise that you have lost it.
> .
> This version of PGP is the `International' version from Stale
> Schumacher. It is somewhat faster, and has more useful features.
> However, it does not have a licence for its use of the RSA
> cryptosystem, on which some nasty people claim a patent.
>
> > Michael: if you must do this please use at least
> > Content-Type: text/x-pgp-message
> > which will tell programs that it's readable text. Better would be
> > Content-Type: text/plain
>
> I do not set any header myself. I just use elm as usual.
In my earlier message, I wrote:
> Craig Sanders writes ("pine doesn't handle pgp signed messages (was Re: New uploads)"):
> > On Wed, 15 May 1996, Michael Meskes wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> ...
> > All i get is
> > [Part 1, Application/X-PGP-MESSAGE 4.7KB]
> > [Can not display this part. Use the "V" command to save in a file]
>
> This is not a bug in Pine (wow!) It's a bug in whatever program
> Michael Meskes is using to generate is messages. They say, in the
> headers:
> Content-Type: application/X-pgp-message
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
>
> The way Pine interprets this is that the message body is not a text
> file; rather it is some weird application-specific gunk that neither
> it nor the user should understand, and the best thing to do is
> probably to save it to a file or something (if it can't find the
> application).
>
> This is an entirely correct interpretation of an entirely incorrect
> header.
>
> Michael: if you must do this please use at least
> Content-Type: text/x-pgp-message
> which will tell programs that it's readable text. Better would be
> Content-Type: text/plain
>
> See the MIME RFCs for more details.
>
> Ian.
Reply to: