Your message dated Fri, 11 Aug 2017 18:38:25 +0000
with message-id <>
and subject line Bug#871627: Removed package(s) from unstable
has caused the Debian Bug report #449594,
regarding emacs22-el: mml2015-pgg-sign does not insert Content-Type: header for 
signed part
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: emacs22-el
Version: 22.1+1-2
Severity: normal

Hash: SHA1

When i use mml-secure-message-sign-pgpmime (C-c C-m s p), in an
up-to-date lenny emacs22 installation, it invokes mml2015-pgg-sign to
sign the active message.

The resulting internal message part (the part that is signed, not the
signature) does not have a Content-Type: header, however.  You can see
an example of one such message here:

Note the lack of a Content-Type: header after the first --=-=-=
separator.  RFC 2045 seems to suggest that a Content-Type: header
should be present for every MIME message, in every part, though it
grants that a default assumption of text/plain is reasonable.  Why not
explicitly declare a Content-Type header before signing?

I noticed this particular issue because pipermail (mailman's archiving
tool) seems to ignore mime parts without an explicit Content-Type.
The message linked above shows up in its original mailman archive
without the message body:

While this blank message presentation is probably a bug in pipermail
(i'm following up with them about it [0]), it would be nice for
pgg-signed messages to include an explicit Content-Type (maybe just
text/plain?) for the body of the messages, to be a little more
"conservative in what you emit".

I've also heard (but not verified) a report from a friend that his
blackberry displays a blank message body when he looks at signed mails
from me.

I realize that the worst bugs here are most likely in other tools, but
it would be good if pgg could play nicer with them as well.

Thanks so much for maintaining these packages in debian!



- -- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages emacs22-el depends on:
ii  emacs22-common                22.1+1-2   The GNU Emacs editor's shared, arc

emacs22-el recommends no packages.

- -- no debconf information

Version: GnuPG v1.4.6 (GNU/Linux)


--- End Message ---
--- Begin Message ---
Version: 24.5+1-11+rm

Dear submitter,

as the package emacs24 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see

The version of this package that was in Debian prior to this removal
can still be found using

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to