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 #812003,
regarding emacs24-el: message-mode repeats non-deterministic cryptographic 
operations in Fcc when sending
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: emacs24-el
Version: 24.5+1-3
Severity: normal
Tags: upstream
Control: forwarded -1

When composing a message with an Fcc: line in emacs message-mode, if
the message has any cryptographic operations set on it
(e.g. mml-secure-message-sign-pgpmime, or
mml-secure-message-encrypt-pgpmime), then those operations are done
distinctly for the message sent via the mail system and the message
stored in Fcc.

This means a few things:

 a) the message body stored in the folder is not a "carbon copy" of
    the message sent to the mail system (surprising!)

 b) Fcc'ed messages must invoke two signatures: once for sending and
    once for storing in Fcc.  (cryptographically sketchy!  why sign
    the same document twice?)

 c) When using a smartcard or prompting for each signature via
    ignore-cache-for-signing in gpg-agent.conf, the user must trigger
    the signature twice (inconvenient)

 d) any encryption choices that require manual intervention (like key
    selection, see must be done
    multiple times as well (more inconvenience)

In the event that some crypto scheme is created which keeps
coordinated peerwise state of all messages sent (e.g. an axolotl
rachet for mail), duplicating a single message like this could
introduce weird out-of-sync states.

The report has already been reported upstream at where i've added some commentary, but
it's not clear to me how to subscribe to that BTS, and no upstream
action has been taken in 6 months (not even a reply).

Any suggestions on how to fix this for users of Fcc with cryptographic
settings would be welcome.

Alternately, if the answer is "don't use Fcc with cryptographic
message-modes", it would be good to provide that warning as well.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing'), (200, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages emacs24-el depends on:
ii  emacs24-common  24.5+1-3

emacs24-el recommends no packages.

emacs24-el suggests no packages.

-- debconf-show failed

--- 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