unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail
Date: Fri, 29 Aug 2014 11:05:19 -0700	[thread overview]
Message-ID: <87lhq7npcw.fsf@maritornes.cs.unb.ca> (raw)


[-- Attachment #0: Type: message/rfc822, Size: 6349 bytes --]

[-- Attachment #1.1: Type: text/plain, Size: 1656 bytes --]

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


live well,
  vagrant


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

Kernel: Linux 3.14-2-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

Versions of packages notmuch depends on:
ii  libc6           2.19-9
ii  libglib2.0-0    2.40.0-4
ii  libgmime-2.6-0  2.6.20-1
ii  libnotmuch3     0.18.1-1
ii  libtalloc2      2.1.1-2
ii  zlib1g          1:1.2.8.dfsg-1

Versions of packages notmuch recommends:
ii  alot           0.3.5-2
ii  gnupg-agent    2.0.25-2
ii  notmuch-emacs  0.18.1-1
ii  notmuch-mutt   0.18.1-1
ii  notmuch-vim    0.18.1-1

notmuch suggests no packages.

-- no debconf information

[-- Attachment #1.2: Type: application/pgp-signature, Size: 818 bytes --]

             reply	other threads:[~2014-08-29 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 18:05 David Bremner [this message]
2014-08-30  7:37 ` [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail Jani Nikula
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=87lhq7npcw.fsf@maritornes.cs.unb.ca \
    --to=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).