Must 'View Source' to See Message

  • lmnmbm

    lmnmbm - 2013-05-22

    For some encrypted messages, Enigmail and Thunderbird will decrypt the message and properly display the plaintext in the message body window. However, for many others, no plaintext is displayed in that window at all. Rather, I have to click Other Actions > View Source to find the ciphertext, copy and paste it into the GPA clipboard (separate application), and decrypt it there. I haven't been able to pinpoint the cause of this issue. Does anyone know about this? Thanks.

  • Ludwig Hügelschäfer

    Hi, this could be different issues, so we need some more information:

    1. Are the mails which are not displayed PGP-inline or PGP/MIME?
    2. Is your mailserver a Microsoft Exchange server?
  • lmnmbm

    lmnmbm - 2013-05-30

    Hi there,

    1. The messages in question appear to be PGP/MIME Version 1.0. However, other messages that decrypt normally in Thunderbird are also PGP/MIME Version 1.0.

    2. I'm paying for a mail service that uses OpenBSD.

  • Patrick Brunschwig

    Can you attach such a message. I suspect that something is wrong with the message.

  • lmnmbm

    lmnmbm - 2013-06-03

    To protect the involved parties, I masked any personal info. I also cut out the ciphertext for convenience.

    Return-path: <*****-41_HTML-180722186-398187-97381-49955@*****.*****.*****.*****>
    Envelope-to: *****@*****.*****.*****
    Delivery-date: Wed, 29 May 2013 16:50:07 +0200
    Received: from _exim by s1.*****.***** with procmailed (Exim 4.76)
        (envelope-from <*****-41_HTML-180722186-398187-97381-49955@*****.*****.*****.*****>)
        id *****-*****-*****
        for *****@*****.*****.*****; Wed, 29 May 2013 16:50:07 +0200
    Received: from [**.**.**.**] (*****.*****.*****.*****)
        by s1.*****.***** with esmtp (Exim 4.76)
        (envelope-from <*****-41_HTML-180722186-398187-97381-49955@*****.*****.*****.*****>)
        id *****
        for *****@*****.*****.*****; Wed, 29 May 2013 16:50:07 +0200
    DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=200608; d=*****.*****.*****;
     h=From:To:Subject:Date:List-Unsubscribe:MIME-Version:Reply-To:Message-ID:Content-Type:Content-Transfer-Encoding; i=**********@*****.*****.*****;
    DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=200608; d=*****.*****.*****;
    Received: by *****.*****.*****.***** id ***** for <*****@*****.*****.*****>; Wed, 29 May 2013 08:50:02 -0600 (envelope-from <*****-41_HTML-180722186-398187-97381-49955@*****.*****.*****.*****>)
    From: "*****" <**********@*****.*****.*****>
    To: <*****@*****.*****.*****>
    Date: Wed, 29 May 2013 08:50:00 -0600
    List-Unsubscribe: <mailto:*****-fd8610711a3c402029-fe2c15787563067f741c76-febb17797d650c7a-fef31d77766c05-feef10797c6101@*****.*****.*****.*****>
    MIME-Version: 1.0
    Reply-To: "*****" <reply-febb17797d650c7a-41_HTML-180722186-97381-49955@*****.*****.*****>
    x-job: 97381_398187
    Message-ID: <*****.xt.local>
    Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="*****-qGyNFUH5-fJrz1zz9"
    This is an OpenPGP/MIME encrypted message (RFC 2440 and 3156)
    content-type: application/pgp-encrypted
    content-transfer-encoding: 7bit
    content-description: PGP/MIME version identification
    Version: 1
    content-type: application/octet-stream; name="msg.asc"
    content-transfer-encoding: 7bit
    content-description: OpenPGP encrypted message
    content-disposition: inline; filename="msg.asc"
    -----BEGIN PGP MESSAGE-----
    Version: GnuPG v1.4.11 (OpenBSD)
    -----END PGP MESSAGE-----
    Last edit: Patrick Brunschwig 2013-06-09
  • Patrick Brunschwig

    Could you please also paste the first few lines of the cyphertext? I'd like to see the message encoding.

    • lmnmbm

      lmnmbm - 2013-06-06



  • Patrick Brunschwig

    I checked the message and if it's not a copy&paste error, then there is something wrong with the content-type specification. The line following the content-type (charset="us-ascii") is wrong.

    It is indented, which means it belongs to the line above, but this cannot be correct. The charset specification is not foreseen for the given content-type (which Enigmail would ignore), but there is no semicolon at the end of the first line, which means it belongs to the boundary specification -- thus the boundary specification is invalid, which breaks decryption.

  • lmnmbm

    lmnmbm - 2013-06-11

    I double checked the original source and it is as it appears in what I pasted.

    So, what entity is responsible for generating that specification? Is it something that would need to be addressed on a case-by-case basis with each problematic sender? I'm trying to confirm whether or not I can fix on the receiving end. Thanks!

  • Patrick Brunschwig

    The message seems to come from a mailing list server (or similar). I cannot be sure, but I assume that this is the culprit.

  • Patrick Brunschwig

    Sorry, I forgot to mention: this is a violation of the relevant specifications (RFC 2882 and RF 3156); I won't create fixes (to be correct: workarounds) for bugs in other software that lead to violations of well-defined and well established specifications.

    • lmnmbm

      lmnmbm - 2013-06-13

      Thanks. While this could be considered a mailing list type of message, some messages with the same problem are known to come from individuals. Here is another excerpt from a content-type specification line:

      Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="*-qGyNFUH5-fJrz1zz9"

      And another:

      Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="*-qGyNFUH5-fJrz1zz9"

      In both instances the final "boundary" line is indented. What are you seeing here?

  • Patrick Brunschwig

    Do I understand correctly, there are two "boundary" parameters for a single "Content-Type:" entry? This is invalid as well. And the missing ";" after the first "boundary" part makes it even worse.

  • Ludwig Hügelschäfer

    Is it possible to identify the software creating such messages?

    • lmnmbm

      lmnmbm - 2013-06-17

      I know that both Outlook and Thunderbird are involved.

      Based on what you told me, I'm wondering if it's because the email service provider is doing the encryption. They are using my public key and PGP to encrypt all messages "at the door" that arrive unencrypted.

  • Ludwig Hügelschäfer

    Then the encryption software, respectively its integration into the mailserver software on providers end is the culprit.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks