Hello fellow Swinogers

To exchange emails containing potentially sensitive customer information with swisscom, we agreed to use PGP encrytped emails.

Now when swisscom is sending an encrypted attachment to us, we get those MIME Headers:

------=_Part_5064522_1012233884.1518535424993 Content-Type: application/octet-stream; name=Attachment1.asc Content-Transfer-Encoding: 7bit X-Content-PGP-Universal-Saved-Content-Type: application/pdf; name=Attachment1.asc X-Content-PGP-Universal-Saved-Content-Description: Example_Filename.pdf X-Content-PGP-Universal-Saved-Content-Disposition: attachment; filename=Attachment1.asc; size=143718; creation-date="Tue, 13 Feb 2018 14:56:05 GMT"; modification-date="Tue, 13 Feb 2018 14:56:05 GMT" X-Content-PGP-Universal-Saved-Content-ID: F73FD4960576014A98D75D430AABA49B@swisscom.com X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=Attachment1.asc

-----BEGIN PGP MESSAGE----- Version: OpenPGP totemomail Comment: totemomail OpenPGP - http://www.totemo.com

[encrypted content]

Well, Neither Claws-Mail nor Firefox with Enigma Plugin do understand those X-Content-PGP Emails which would specify the correct content type and file name and just merely show a binary "Attachment1.asc" attachement. Of course, as experienced user reading the email source, you can save this to disk and then open it with a PDF reader, but using encrypted email should be easier than that :-)

So I contacted the totemo support and they told me, that every PGP enabled email client should be able to correctly extract mime-type and filename from the X-Content-PGP Headers.

Well I have found: https://www.ietf.org/rfc/rfc4880.txt https://binblog.info/2008/03/12/know-your-pgp-implementation/

Well, I know no clients which support RFC4880 when generating or decoding PGP encrypted emails. How about the SWINOG Community?

Mit freundlichen Grüssen

-Benoît Panizzon-