Re: can't read sent encrypted mail

[Kevin J. McCarthy]

On Sat, Oct 08, 2016 at 02:46:42AM +0200, Peter P. wrote:
> Interesting! man muttrc tells me that the default for crypt_use_gpgme is no.

Yes, but I believe they changed the system muttrc to enable it (likely
in /etc/Muttrc.d/gpg.rc.  Your own muttrc is read afterwards and so can
override that setting.

> Nevertheless when I
>   unset crypt_use_gpgme
> or
>   set unset crypt_use_gpgme=no
> the problem remains.

Which problem are you speaking of?  This will not magically allow you to
read emails encrypted in the recent past using gpgme (that therefore
were not also encrypted to you).  It should make emails sent henceforth
be encrypted to you again.

> How could I debug this further?

Well, first I am assuming that this is a recent change in behavior, and
that prior to the mutt upgrade in Debian you had no trouble reading your
encrypted emails sent to others.

You might check that those older sent emails are still readable by you.

To make sure the option is off, type
  :set ?crypt_use_gpgme
and mutt should echo back 'crypt_use_gpgme is unset'

Also note that this option needs to be (un)set in your muttrc and mutt
must to be restarted; you can't change it interactively to effect.

> Btw, is there any advantage of switching to gpgme?

The classic interface has some built-in size limits to the number of
recipients.  It also requires setting $pgp_use_gpg_agent appropriately
depending on if you are using gpg 1.4, 2.0, or 2.1.

However, the classic interface is better tested.  There's a lot of gpgme
code that I haven't looked at in detail, and there will likely be more
bugs that need to be shaken out of it.

> How would I add my own key to the encryption in gpgme?

You could try adding an 'encrypt-to' setting in your ~/.gnupg/gpg.conf file.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: [OT?] please do not tag messages as spam

[Claus Assmann]

Sorry about that, it's actually something at the mailing list server
that does this : it not only adds X-FidoGuard-... headers, but
also munges the Subject with some utf-8 token (which seems like a
useless "encoding"). That software obviously has too many false-positives
:-(

Re: can't read sent encrypted mail

[Peter P.]

Hi Kevin,

* Kevin J. McCarthy  [2016-10-08 01:44]:
> On Fri, Oct 07, 2016 at 07:46:10PM +0200, Peter P. wrote:
> > Hi list,
> > 
> > I am having a strange problem with mutt (NeoMutt 1.7.0 on debian
> > testing) and gpg (GnuPG) 2.1.15
> 
> Debian switched to using GPGME by default.  GPGME does not look at the
> various $pgp_* commands, so your changes made in your muttrc are not
> taking effect.
> 
> Add 'unset crypt_use_gpgme' to your muttrc, to start using your
> pgp_encrypt_sign_command again.
Interesting! man muttrc tells me that the default for crypt_use_gpgme is no.

Nevertheless when I 
unset crypt_use_gpgme
or
set unset crypt_use_gpgme=no
the problem remains.

How could I debug this further?
Btw, is there any advantage of switching to gpgme? How would I add my
own key to the encryption in gpgme?

Thanks again!
Peter

[SPAM?] [OT?] please do not tag messages as spam

[Claus Assmann]

IMNSHO it's rather annoying when people send mail to the list and
add a [SPAM] tag to the Subject: header.

If it were spam, why would you send it to the list?

[maybe the mailing list SW could filter/reject such mails :-) ...]

-- 
Reply-To: is set, please do not Cc' me.

Re: [SPAM?] some elements keep solid black background

[Kevin J. McCarthy]

On Sat, Oct 08, 2016 at 12:09:10AM +0200, nfb wrote:
> There are, however, some parts that preserve a solid black background,
> like the "[-- Attachment ... --]", "[-- appication/zip ... --]",
> "[-- Type ... --]", "[-- Autoview using ... --]" strings,

Those should be covered by the 'attachment' color object.  Have you
tried setting the background for that to default?

> or the empty bottom of the mail body when you scroll al the way down
> (even after the signature, if any).

This should be covered by the 'tilde' color object.

> And shouldn't the directive "color normal default default" (which i
> obviously have in my rc file) already cover this?

No, that won't change the default for all the different color objects.
Normal just represents "everything else" not covered by the other color
objects.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: can't read sent encrypted mail

[Kevin J. McCarthy]

On Fri, Oct 07, 2016 at 07:46:10PM +0200, Peter P. wrote:
> Hi list,
> 
> I am having a strange problem with mutt (NeoMutt 1.7.0 on debian
> testing) and gpg (GnuPG) 2.1.15

Debian switched to using GPGME by default.  GPGME does not look at the
various $pgp_* commands, so your changes made in your muttrc are not
taking effect.

Add 'unset crypt_use_gpgme' to your muttrc, to start using your
pgp_encrypt_sign_command again.

Unfortunately, emails you've already sent with gpgme enabled will not be
readable by you.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

[SPAM?] some elements keep solid black background

[nfb]

Hi,
this is a question i have had aside for long time, so now that i
subscribed to the mailing listi, and after having searched enough
on the web, without apparent results, i will try to ask to you.

In mutt i have styled all the relevant parts to have a default
background, so that i see the native background color of my terminal.
There are, however, some parts that preserve a solid black background,
like the "[-- Attachment ... --]", "[-- appication/zip ... --]",
"[-- Type ... --]", "[-- Autoview using ... --]" strings, or the empty
bottom of the mail body when you scroll al the way down (even after
the signature, if any).
I don't know if you need a screenshot for them, but i think they are
pretty common strings, so i guess you know what i'm talking about.
My question is, is there a way to set a color for these elements? And
shouldn't the directive "color normal default default" (which i
obviously have in my rc file) already cover this?

Thanks for your time.

[SPAM?] Re: can't read sent encrypted mail

[Peter P.]

Adding more information below.

* Peter P.  [2016-10-07 19:46]:
> Hi list,
> 
> I am having a strange problem with mutt (NeoMutt 1.7.0 on debian
> testing) and gpg (GnuPG) 2.1.15
> 
> Mail that I encrypt with someone else's key, and also with my own one,
> is unreadable by myself afterwards in my Sent folder. Mutt gives a
> rather short
>   Could not decrypt PGP message
> followed by 
>   Could not copy message
Messags that I encrypt to myself only are successfully decrypted.
Thanks, P

can't read sent encrypted mail

[Peter P.]

Hi list,

I am having a strange problem with mutt (NeoMutt 1.7.0 on debian
testing) and gpg (GnuPG) 2.1.15

Mail that I encrypt with someone else's key, and also with my own one,
is unreadable by myself afterwards in my Sent folder. Mutt gives a
rather short
Could not decrypt PGP message
followed by 
Could not copy message

mutt -d 5 gives the following in .muttdebug
Entering pgp_encrypted handler
../../crypt-gpgme.c:2591: mutt_mktemp returns 
"/tmp/mutt-hostname-1000-26184-6735641325734396222".
Could not decrypt PGP message
which I can't make much sense of and which doesn't yield useful results
in a web search.

I have a .mutt/mutt_gpg.rc which has, amongst other lines
set pgp_encrypt_sign_command="/usr/lib/mutt/pgpewrap gpg
%?p?--passphrase-fd 0? --pi nentry-mode=loopback --batch --quiet
--no-verbose --textmode --output - --encrypt -- sign %?a?-u %a? --armor
--always-trust --encrypt-to 0xmyOwnKey -- -r %r -- %f"
and I sign/encrypt using my own key as well (--encrypt-to). 

PS: I discovered that there is an /etc/muttrc.d/ directory present on my
Debian system, which I was not aware of, and it holds an
/etc/muttrc.d/gpg.rc file. I wonder which one is given precedence?
Starting mutt with the -n flag (bypass system configuration file) does
not change the problematic behavior.

I am aware that debian switched to neomutt, and that gpg in mutt might
have switched to gpgme and its possible different configuration options. 
But how do I go about debugging all this? Any ideas are well appreciated!
Thank you for your help!
Peter

Re: Mailbox closed with gmail account

[Grant Edwards]

On 2016-10-07, tristero tristero  wrote:
> Hello,
> I'm trying to configure Mutt to access a gmail account. I had a look
> at some tutorials and configurations and right now this is my .muttrc:
>
> set imap_user = "myu...@gmail.com"
> set imap_pass = "xx"
>
> set smtp_url = 'smtp://myu...@smtp.gmail.com:587/'
> set smtp_pass='xxx'
>
> set from = 'myu...@gmail.com'
> set realname = 'Name'
>
> set folder="imaps://imap.gmail.com"
> set spoolfile="imaps://imap.gmail.com/INBOX"
> set record="imaps://imap.gmail.com/[Gmail]/Sent Mail"
> set postponed="imaps://imap.gmail.com/[Gmail]/Drafts"
>
> set header_cache = "~/.mutt/cache/headers"
> set message_cachedir = "~/.mutt/cache/bodies"
> set certificate_file = "~/.mutt/certificates"
>
> set move = no
> set smtp_authenticators = 'gssapi:login'
> set imap_keepalive = 120
> set imap_idle=yes
> set mail_check = 1


> The problem is that after a couple of minutes of inactivity, it
> disconnects and it displays the message "Mailbox closed". I've already
> looked around for a solution and as you can see at the end of my
> configuration I tried setting a very small time interval to keepalive
> and also mail_check, but still nothing.

Here's what I use:

  set mail_check=90
  set timeout=15
  set imap_keepalive=30

AFAICT, I don't have imap_idle enabled.  I use mutt with gmail/imap
almost exclusively, and never notice any issues.  But, I don't usually
leave mutt sitting open when I'm not actually reading or sending mail.

-- 
Grant Edwards   grant.b.edwardsYow! I'm having an
  at   EMOTIONAL OUTBURST!!  But,
  gmail.comuh, WHY is there a WAFFLE
   in my PAJAMA POCKET??

Re: Mailbox closed with gmail account

[lists]

On Fri, Oct 07, 2016 at 11:13:05AM +0200, tristero tristero wrote:
> Hello,

> The problem is that after a couple of minutes of inactivity, it
> disconnects and it displays the message "Mailbox closed". I've already
> looked around for a solution and as you can see at the end of my
> configuration I tried setting a very small time interval to keepalive
> and also mail_check, but still nothing.
> Is there a solution to this?

I am personally not a user of gmail so I am not sure if this is a
client-contrallable option to begin with as it makes to close
long-standing IMAP connections on the server side (at least with free
email products...) but most people I know about use mutt + gmail with
tools like offlineimap, fetchmail or similar which sync the IMAP folders
to local storage in regular intervals (and back if you make local
changes). This could serve as a workaround if this can't be solved in
terms of client-side configuration.

Mailbox closed with gmail account

[tristero tristero]

Hello,
I'm trying to configure Mutt to access a gmail account. I had a look
at some tutorials and configurations and right now this is my .muttrc:

set imap_user = "myu...@gmail.com"
set imap_pass = "xx"

set smtp_url = 'smtp://myu...@smtp.gmail.com:587/'
set smtp_pass='xxx'

set from = 'myu...@gmail.com'
set realname = 'Name'

set folder="imaps://imap.gmail.com"
set spoolfile="imaps://imap.gmail.com/INBOX"
set record="imaps://imap.gmail.com/[Gmail]/Sent Mail"
set postponed="imaps://imap.gmail.com/[Gmail]/Drafts"

set header_cache = "~/.mutt/cache/headers"
set message_cachedir = "~/.mutt/cache/bodies"
set certificate_file = "~/.mutt/certificates"

set move = no
set smtp_authenticators = 'gssapi:login'
set imap_keepalive = 120
set imap_idle=yes
set mail_check = 1

The problem is that after a couple of minutes of inactivity, it
disconnects and it displays the message "Mailbox closed". I've already
looked around for a solution and as you can see at the end of my
configuration I tried setting a very small time interval to keepalive
and also mail_check, but still nothing.
Is there a solution to this?

Thank you