From: Jani Nikula <jani@nikula.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail
Date: Sat, 30 Aug 2014 10:37:43 +0300 [thread overview]
Message-ID: <87k35q2zso.fsf@nikula.org> (raw)
In-Reply-To: <87lhq7npcw.fsf@maritornes.cs.unb.ca>
On Thu, 28 Aug 2014, Vagrant Cascadian <vagrant@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. mode=signinvalidencrypt, notmuch happily and without warning
> sends the mail unencrypted.
>
> 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 set up in ~/.emacs, not sure what all else might be coming
> into play:
>
> '(message-setup-hook (quote (mml-secure-message-sign)))
> '(notmuch-crypto-process-mime t)
I'm inclined to think this is a bug in message-mode. But we should
probably try to see what we could do to mitigate this.
As a workaround of sorts, I'd suggest not messing with the #secure tag
manually. Instead, you can use mml-secure-message-sign and
mml-secure-message-sign-encrypt to change the mode.
BR,
Jani.
next prev parent reply other threads:[~2014-08-30 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:05 [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail David Bremner
2014-08-30 7:37 ` Jani Nikula [this message]
2014-09-02 5:57 ` Daniel Kahn Gillmor
2014-09-02 8:02 ` Tomi Ollila
2014-11-12 20:17 ` David Edmondson
2014-11-29 19:09 ` David Bremner
2014-12-01 6:41 ` David Edmondson
2014-12-01 6:45 ` David Bremner
2014-12-01 7:16 ` David Edmondson
2016-02-08 17:52 ` David Edmondson
2021-12-26 11:28 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k35q2zso.fsf@nikula.org \
--to=jani@nikula.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).