Menu ▾ ▴

#1048 Decrypted mail has empty Content-Type in the MIME part.

fixed
nobody
None
2.1.5
Minor
68.3.0
2.2.19
All
2.1.8
nobody
2020-08-29
2020-01-23
Gerrit M. Albrecht
No

I have here an automatic mailing system which sends PGP encrypted messages. The E-Mails are multipart/mixed, first part is a PGP encrypted quoted-printable text/html, second one is an encrypted attachment with type application/xml with base64 and Content-Disposition: attachment set. The E-Mail (decrypted on show) displays its content as text (not html) and the attachment opens as base64 encoded PGP message (a texteditor opens and shows the base64 encoded BEGIN/END-PGP block). Thats not okay (maybe another bug), but acceptable, because I'm only interested in the decrypted E-Mail. I use a filter and auto-decrypt into a folder and these E-Mails are then processed by an external script (extract attachment, XSL transform, handle content). The E-Mail decrypts fine. The XML attachment opens with its stylesheet on click, but the mail content of the decrypted mail has the following header (in the corresponding MIME part):

Content-Type: ; charset=utf-8
Content-Transfer-Encoding: 8bit

It should be (as in the encoded mail):

Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

If I add "text/html" manually, it displays also well.

2 Attachments
Example E-Mail (not complete).txt
protokoll.txt

Discussion

  • Gerrit M. Albrecht

    Gerrit M. Albrecht - 2020-01-23
     

    Last edit: Gerrit M. Albrecht 2020-01-23

  • Gerrit M. Albrecht

    Gerrit M. Albrecht - 2020-01-23
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,4 +1,4 @@
-I have here an automatic mailing system which sends PGP encrypted messages. The E-Mails are multipart/mixed, first part is a quoted-printable text/html, second one is an attachment with type application/xml with base64 and Content-Disposition: attachment set. The E-Mail (decrypted on show) displays its content as text (not html) and the attachment opens as base64 encoded PGP message (a texteditor opens and shows the base64 encoded BEGIN/END-PGP block). Thats not okay (maybe another bug), but acceptable, because I'm only interested in the decrypted E-Mail. I use a filter and auto-decrypt into a folder and these E-Mails are then processed by an external script (extract attachment, XSL transform, handle content). The E-Mail decrypts fine. The XML attachment opens with its stylesheet on click, but the mail content of the decrypted mail has the following header (in the corresponding MIME part):
+I have here an automatic mailing system which sends PGP encrypted messages. The E-Mails are multipart/mixed, first part is a PGP encrypted quoted-printable text/html, second one is an encrypted attachment with type application/xml with base64 and Content-Disposition: attachment set. The E-Mail (decrypted on show) displays its content as text (not html) and the attachment opens as base64 encoded PGP message (a texteditor opens and shows the base64 encoded BEGIN/END-PGP block). Thats not okay (maybe another bug), but acceptable, because I'm only interested in the decrypted E-Mail. I use a filter and auto-decrypt into a folder and these E-Mails are then processed by an external script (extract attachment, XSL transform, handle content). The E-Mail decrypts fine. The XML attachment opens with its stylesheet on click, but the mail content of the decrypted mail has the following header (in the corresponding MIME part):

 Content-Type: ; charset=utf-8
 Content-Transfer-Encoding: 8bit
     

  • Patrick Brunschwig

    Patrick Brunschwig - 2020-01-23

    Is the following summary correct: you use a filter to decrypt an email into a folder, and the filter destroys the content-type of the decrypted message part?

     

    • Gerrit M. Albrecht

      Gerrit M. Albrecht - 2020-01-24

      The same error occurs if the email is decrypted manually using "Decrypt in folder". Its not the filter.

      But the filter seems to have another bug: Some e-mails with the structure described decrypt their content (the MIME part of the content, not the attachment) completely empty. This occurs sporadically and accidentally and the remedy is to simply decrypt this email manually (into a folder) again. This works always. I will try to get a log, but its not possible to enforce this bug. We are an authority and I see such empty mails from time to time if users complaining about getting a file with blank pages for processing...

       

  • Patrick Brunschwig

    Patrick Brunschwig - 2020-01-24

    It's actually the same. The function "decrypt to folder" triggers a one-time (ad-hoc) filter action for the selected messages.

     

  • Patrick Brunschwig

    Patrick Brunschwig - 2020-08-29
    • status: open --> fixed
    • Fixed in version: --- --> 2.1.8
     

Log in to post a comment.