Re: pgp attachment problem

2016-10-30 Thread Simon Ruderich
On Mon, Oct 17, 2016 at 11:28:02PM +0200, martin boeder wrote:
> Hi,
>
> I'm using mutt since a long time ago and started to use pgp
> now. It works fine for me, except one thing: If I get an
> message with an attachment mutt shows me the attachment inline
> only. Like this:
>
> [snip]

Hello,

I never had any issues with attachments and PGP (or I fixed them
a long time ago and don't remember). Could you attach an example
mail with the issue as mbox so I could try it with my setup?

What is the minimal muttrc for your gpg setup (don't forget
/etc/Mutt.d which might affect your settings)?

Regards
Simon
-- 
+ Privatsphäre ist notwendig
+ Ich verwende GnuPG http://gnupg.org
+ Öffentlicher Schlüssel: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature


pgp attachment problem

2016-10-17 Thread martin boeder
Hi,
 
I'm using mutt since a long time ago and started to use pgp now. It works fine 
for me,
except one thing: If I get an message with an attachment mutt shows me the 
attachment
inline only. Like this:
 
...

[-- BEGIN PGP MESSAGE --]   
   
Content-Type: multipart/mixed; boundary="Ui8oIDq6MW9GU3SUM5K8n8J3PoOTdg4xM";
 protected-headers="v1"
From: f...@bar.de
To: foo-...@bar.de
Message-ID: 
Subject: Testmail
References: <20161016233834.GA10087@host.localdomain>
In-Reply-To: <20161016233834.GA10087@host.localdomain>
--Ui8oIDq6MW9GU3SUM5K8n8J3PoOTdg4xM
Content-Type: multipart/mixed;
 boundary="3B1EE4EBF561C851E448F340"
This is a multi-part message in MIME format.
--3B1EE4EBF561C851E448F340
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
 
Email content text
 
--3B1EE4EBF561C851E448F340
Content-Type: image/jpeg;
 name="Image.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Image.jpg"
/9j/4AAQSkZJRgABAQEAYABgAAD//gATQ3JlYXRlZCB3aXRoIEdJTVD/2wBDABYPERMRDhYT
EhMZFxYaITckIR4eIUQwMyg3UEZUU09GTUxYY39sWF54X0xNbpZweIOHjpCOVmqcp5uKpn+L
jon/2wBDARcZGSEdIUEkJEGJW01biYmJiYmJiYmJiYmJiYmJiYmJiYmJiYmJiYmJiYmJiYmJ
iYmJiYmJiYmJiYmJiYmJiYn/wgARCAF6AfMDAREAAhEBAxEB/8QAGQABAAMBAQAA
...
 
Somewhere I'd read mutt could handle that. The FAQ recommends me NOT to use 
procmail. [1]
Unfortunately I can't use a found patch (version conflict). [2] And 
mailcap-hints doesn't look helpful. [3]
I'd spend a lot of hours for searching, but couldn't find anything helpful at 
least.I'm using
mutt version 1.5.24-r2 on a Gentoo box. Or is the problem fixed since 1.6.0? [4]
 
Thanks in advance, Martin
 
[1] https://dev.mutt.org/trac/wiki/MuttFaq/Encryption
[2] 
https://dev.mutt.org/trac/changeset/21a08f9abc80d7ea0b3dc0a9f8fa2013c7446f5a[https://dev.mutt.org/trac/changeset/21a08f9abc80d7ea0b3dc0a9f8fa2013c7446f5a]
[3] 
https://github.com/cbracken/mutt/blob/master/.mutt/mailcap[https://github.com/cbracken/mutt/blob/master/.mutt/mailcap]
https://www.spinnaker.de/mutt/mailcap
[4] http://www.mutt.org/doc/UPDATING[http://www.mutt.org/doc/UPDATING]