Your message dated Sun, 25 Sep 2016 08:00:48 +0000
with message-id <[email protected]>
and subject line mutt: would be nice to have a pattern for inline-encrypted mail
has caused the Debian Bug report #302010,
regarding mutt: would be nice to have a pattern for inline-encrypted mail
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 [email protected]
immediately.)
--
302010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302010
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.5.8-1
Severity: wishlist
It would be nice to have a pattern (like ~g and ~G) that matches mail that is
encrypted "inline".
As an example of how it could be very useful...
Some of the people I send mail to use pine and as such can only decrypt inline
pgp messages. I would like to be able to make sure that when I send messages to
them, I send the messages encrypted/signed inline. This generally works by
using a pattern of '~C [email protected]', but I would like this to
also trigger when adding them to the sending list in the compose menu (i.e.
from a send2-hook). Within a send2-hook, changing the encryption settings
(which requires the use of "push") triggers the send2-hooks again. Therefore, I
can't just use '~C pineusingfriend' as the pattern to match, because that would
cause an infinite loop (every time, the command to change the encryption
settings causes the send2-hooks to be triggered again). Thus, something like
this:
send2-hook '~C pineusingfriend' 'push pfpbpi'
causes an infinite loop. If, however, there was something like ~I that matched
"pgp inline messages", I could use:
send2-hook '~C pineusingfriend ! ~I' 'push pfpbpi'
and it would work properly.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (100, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.3
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages mutt depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libdb4.3 4.3.27-2 Berkeley v4.3 Database Libraries [
ii libgnutls11 1.0.16-9 GNU TLS library - runtime library
ii libidn11 0.5.13-1.0 GNU libidn library, implementation
ii libncursesw5 5.4-4 Shared libraries for terminal hand
ii libsasl2 2.1.19-1.5 Authentication abstraction library
ii qmail [mail-transport-agent 1.03-31 Secure, reliable, efficient, simpl
-- no debconf information
--- End Message ---
--- Begin Message ---
tag 302010 +wontfix
thanks
The crypto gpg code within mutt has been superseeded by the use of gpgme, which
is more solid and secure. As a result of that inline encryption/decryption is no
longer supported (unless you manually unset gpgme, which we don't advise).
I'm closing this bug as a result of that.
--- End Message ---
