On Sat, Nov 29 2014, David Bremner wrote: > David Edmondson <email@example.com> writes: > >> On Tue, Sep 02 2014, Tomi Ollila wrote: >>> On Tue, Sep 02 2014, Daniel Kahn Gillmor <firstname.lastname@example.org> wrote: >>> >>>> On 08/30/2014 03:37 AM, Jani Nikula wrote: >>>>> I'm inclined to think this is a bug in message-mode. >>>> >>>> I agree it's a bug in message-mode, not in notmuch itself. >>> >>> I think it might be here: >>> >>> http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/head:/lisp/gnus/mml.el#L258 >>> >>> (it takes time to load, please wait...) >>> >>> If cond does not match, then don't fail... >> >> This looks to have been fixed in emacs at the end of September 2014. > > Right, this fix was released in emacs 24.4 > > I'm a little torn what to do here. On the one hand the upstream change > fixes the bug as reported. On the other hand, if something corrupts the > #secure tag (e.g., by deleting a letter), then the message is still sent > un-uncrypted. I'm unclear on what you mean. Is it that "upgrade to 24.4" is not a good enough answer, because we are still leaving pre-24.4 people out in the cold?