Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

David Bremner writes: > > i.e. #secure method=pgpmime mode=signinvalidencrypt will end up > sending an encrypted message (with the <>, of course). > > It seems like it should error out if the mode= is set to an invalid or > unknown value, rather than sending mail in the clear. > > I've got this

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

[Raking over history...] On Sat, Nov 29 2014, David Bremner wrote: > David Edmondson writes: > >> On Tue, Sep 02 2014, Tomi Ollila wrote: >>> On Tue, Sep 02 2014, Daniel Kahn Gillmor wrote: >>> On 08/30/2014 03:37 AM, Jani Nikula wrote: > I'm

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

David Edmondson writes: >> 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

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Mon, Dec 01 2014, David Bremner wrote: > David Edmondson writes: > >>> 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

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Sat, Nov 29 2014, David Bremner wrote: > David Edmondson writes: > >> On Tue, Sep 02 2014, Tomi Ollila wrote: >>> On Tue, Sep 02 2014, Daniel Kahn Gillmor 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

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Sat, Nov 29 2014, David Bremner wrote: David Edmondson d...@dme.org writes: On Tue, Sep 02 2014, Tomi Ollila wrote: On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 08/30/2014 03:37 AM, Jani Nikula wrote: I'm inclined to think this is a bug in message-mode. I

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

David Edmondson d...@dme.org writes: 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

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Mon, Dec 01 2014, David Bremner wrote: David Edmondson d...@dme.org writes: 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

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

David Edmondson writes: > On Tue, Sep 02 2014, Tomi Ollila wrote: >> On Tue, Sep 02 2014, Daniel Kahn Gillmor 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. >>

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

David Edmondson d...@dme.org writes: On Tue, Sep 02 2014, Tomi Ollila wrote: On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net 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

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Tue, Sep 02 2014, Tomi Ollila wrote: > On Tue, Sep 02 2014, Daniel Kahn Gillmor 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: > >

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Tue, Sep 02 2014, Tomi Ollila wrote: On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net 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

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Tue, Sep 02 2014, Daniel Kahn Gillmor 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:

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

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. > As a workaround of sorts, I'd suggest not messing with the #secure tag > manually. Instead, you can use mml-secure-message-sign and >

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net 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:

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

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. As a workaround of sorts, I'd suggest not messing with the #secure tag manually. Instead, you can use mml-secure-message-sign and

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Thu, 28 Aug 2014, Vagrant Cascadian wrote: > When sending mail from notmuch-emacs interface, I usually use pgpmine > signatures, but sometimes I want to send a signed encrypted message, so > I manually edit the mode=sign to mode=signencrypt ... but if I make a > typo, i.e.

Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

On Thu, 28 Aug 2014, Vagrant Cascadian vagr...@debian.org wrote: When sending mail from notmuch-emacs interface, I usually use pgpmine signatures, but sometimes I want to send a signed encrypted message, so I manually edit the mode=sign to mode=signencrypt ... but if I make a typo, i.e.

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

An embedded message was scrubbed... From: Vagrant Cascadian Subject: Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail Date: Thu, 28 Aug 2014 21:17:51 -0700 Size: 6392 URL:

[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail

---BeginMessage--- Package: notmuch-emacs Version: 0.18.1-1 Severity: normal Thanks for notmuch-emacs! When sending mail from notmuch-emacs interface, I usually use pgpmine signatures, but sometimes I want to send a signed encrypted message, so I manually edit the mode=sign to mode=signencrypt