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
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
:-(
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.
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.
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'
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
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
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
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
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
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
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 =
12 matches
Mail list logo