Decrypting S/MIME messages using Outlook 2013

  • Resolved Oelder

    (@carstenkegel)


    8 years, 11 months ago

    I am using a Contact Form 7 to allow any visitor of my site to send messages to exactly one registered user, and I have pasted in this users public S/MIME certificate into its profile. And voilà: the messages received from the contact form are encrypted.

    Unfortunately, the received messages are not decrypted in Outlook 2013 but are shown as plain ciphertext, and there is no key or lock sign indicating that the message is encrypted. The S/MIME certificates are properly installed in Outlook as verified by communication with another e-mail address.

    It doesn’t make a difference whether a public S/MIME certificate is given for the admin under Dashboard → Settings → Email Encryption.

    I have no idea what to do to get the messages decrypted. Any help is really appreciated.

    • This topic was modified 8 years, 11 months ago by Oelder. Reason: Correct spelling
    • This topic was modified 8 years, 11 months ago by Oelder. Reason: Added informations
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Meitar

    (@meitar)

    8 years, 11 months ago

    I don’t have Outlook 2013 so I can’t test this myself. It would help if you provided some technical details about the problem, rather than just a description that it occurs. For instance: a screenshot of what it looks like in Outlook, the raw source of the email sent from the plugin and then the raw source of the email received in Outlook, the public S/MIME cert to which you are encrypting, and so on.

    You might also consider trying to send and/or receive S/MIME encrypted emails with a different email client besides Outlook, and then a different tool besides this plugin. If other tools also do not work, the problem is not with this plugin, but with your instance of Outlook, of course.

    These are some extremely basic, common-sense troubleshooting steps that you should always do before you post to support forums. No one can do anything to help you without the information needed to do so.

    Thread Starter Oelder

    (@carstenkegel)

    8 years, 11 months ago

    I don’t know how to get access to the raw source of the e-mail sent and the raw source of the e-mail received, but the headerlines of the message received looks as follow:

    X-Envelope-From: <[email protected]>
    X-Envelope-To: <[email protected]>
    X-Delivery-Time: 1499973568
    X-UID: 14
    Return-Path: <[email protected]>
    Authentication-Results: strato.com 1;
    spf=none
    smtp.mailfrom=”[email protected]”;
    dkim=pass
    header.d=naturheilkunde-kegel.de;
    domainkeys=none;
    dkim-adsp=pass
    header.from=”[email protected]”
    X-Strato-MessageType: email
    X-RZG-CLASS-ID: mi00
    Received-SPF: none
    client-ip=2a01:238:20a:202:5310::5;
    helo=”cg6-p00-ob.smtp.rzone.de”;
    envelope-from=”[email protected]”;
    receiver=smtpin.rzone.de;
    identity=mailfrom;
    Received: from cg6-p00-ob.smtp.rzone.de ([IPv6:2a01:238:20a:202:5310::5])
    by smtpin.rzone.de (RZmta 41.1 OK)
    with ESMTPS id r073dct6DJJR69I
    (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA))
    (Client CN “*.smtp.rzone.de”, Issuer “TeleSec ServerPass DE-2” (verified OK (+EmiG)))
    (Client hostname verified OK)
    for <[email protected]>;
    Thu, 13 Jul 2017 21:19:27 +0200 (CEST)
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1499973567;
    l=3158; s=domk; d=naturheilkunde-kegel.de;
    h=Content-Transfer-Encoding:Content-Type:MIME-Version:
    Content-Transfer-Encoding:Content-Disposition:MIME-Version:Reply-To:
    From:Date:Subject:To;
    bh=x5fYYKkzM054fDTpr+YtHW5+O1XLLgVSwWmz1a4HF0w=;
    b=yeLdovUVtWSu8vbtZ8yLf3ykl/vOAECBcUR8fVhkxtyQlW2rohv9NDAm8ro9z7tOfb
    5SdVk6xG66nMa2uipjhcqHtemYHa7FyJDBxU0ER97HCiCkuhq3ZDapCBgDtiKiOwAyrN
    fEp078qhLgIC57Bc9jQuE8CdMUuPqno1JxN74=
    X-RZG-CLASS-ID: cg00
    Received: from bomar.store.d0m.de ([192.168.43.233])
    by chrootmail.store (RZmta 41.1 OK)
    with ESMTP id U016f9t6DJJR40A
    for <[email protected]>;
    Thu, 13 Jul 2017 21:19:27 +0200 (CEST)
    Received: by bomar.store.d0m.de (Postfix, from userid 100)
    id D611DB4B6; Thu, 13 Jul 2017 21:19:27 +0200 (CEST)
    To: [email protected]
    Subject: Naturheilpraxis Kegel “Test”
    Date: Thu, 13 Jul 2017 19:19:27 +0000
    From: Carsten Kegel <[email protected]>
    Reply-To: [email protected]
    Message-ID: <[email protected]>
    X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
    X-WPCF7-Content-Type: text/html
    MIME-Version: 1.0
    Content-Disposition: attachment; filename=”smime.p7m”
    Content-Transfer-Encoding: base64
    MIME-Version: 1.0
    Content-Type: multipart/alternative;
    boundary=”b1_5a186f176190bd12f028b4deeb999e20″
    Content-Transfer-Encoding: 8bit
    X-RZG-SCRIPT: :P28WfFC8JrA0JY4UkyfhUWv+YuCloWhyOLk77zZraDNPI4MwvWt9TLCHf4rnRR8urWyB3T2y1g7JSUIvZRigp8JhCkp8blnsNk5Abh1QVjHiIGMsFHI2z4xm0kCa/MEcN+82sZSMS14wakJ/HA==

    Plugin Author Meitar

    (@meitar)

    8 years, 11 months ago

    I don’t know how to get access to the raw source of the e-mail sent and the raw source of the e-mail received

    :\ Did you try Google? http://lmgtfy.com/?q=how+to+view+email+source+in+outlook

    the headerlines of the message received looks as follow:

    That’s not enough.

    Thread Starter Oelder

    (@carstenkegel)

    8 years, 11 months ago

    And the message content received is this:

    MIIEFQYJKoZIhvcNAQcDoIIEBjCCBAICAQAxggF5MIIBdQIBADBdMFExKTAnBgNV BAMMIFZvbGtzdmVyc2NobHVlc3NlbHVuZyBQcml2YXRlIENBMRcwFQYDVQQKDA5G cmF1bmhvZmVyIFNJVDELMAkGA1UEBhMCREUCCGXxueuhTp23MA0GCSqGSIb3DQEB AQUABIIBAIPyqxR3MY0tgQhIpSte5sWeUiCC3VUIauA7/K2zxU+JxEsZNMqqM838 WpaMFCmdZsecG3+aJyw+IXafv9D87CaHoCj/S7AP6Sa9vilz0ic9KQQLRBf+Dzxf H8NAHPjNCBdnTmDAdyrNxIxtgGmpcWZcLAhigKmU/r4xrKTZZD1dCj6DpIZM3lah j4BBkLv0UIXXL3avrGKWfZVlrYwhtccLo2BvXdkbdmACHCIHKPbAlj8cphdkjC5y FpA5q/wt2iPOE6GyzBFCTxdaSGMOESUDk5Nhqinnq/dHvSp+zg9kt8ymqk86yg/b 4wHDasHXjiCiJxepNtfY1cYubGA4chYwggJ+BgkqhkiG9w0BBwEwHQYJYIZIAWUD BAEqBBD0TT67yuLKizoXjFBrTL6ggIICUNt4o0c8f+IMriqvzxjFb8QRLT8ypuPs 7O4TlqKwy5+0xYQBilNuePfoNXn0B0Ml7Df2P/Hqu1+CB9GJ5ls3SrladtOK9DTl 2oRzNgRYwyK7b2eHimu9cp/vIGA9vYEtWIv2g4B3v/BpbpRmHfoRkwsyoHpgBu0H lCa4JytTPCNY4yaHcC+MD3YcJamUuduL8OMfnrmZbBdvf3n+Dway9hIje30KBB5O txcrgJ2uGnH6VFTHCRZ0vrprBk3g56XKLaF7oyE26nzjumwi9dFYI0R3zFDB4QjY TYxzSobxNaXI4EZDGZ+BYqaS/vOLk2C11SlVS88sH8JcDG7tpLU9KK55SnuuvmZK 6J3cQO6hRKMtq4Dhxstc+VwKO9NXMLXGYQLaJRs6A3fCWJO72PZ/dqvz0QJ2NpjC Lqj89ECY1W3QXhhl+fKrAgMa8OTVDV/igU5okyfd92WRFIgOMPw2Qn6Bl762da0K 5o6Inzzzozvnv0rbQTLDaf8oZ8BEH3nOFXqhLuXAnh/0SqNif/AJRhTJrPDtjgzO uzK2SZDygONZUnoPxczur98jW3LvuDR/p01LKtKyagyPws5jMUrNitDIA+Q/bZh0 RpqvQLhMS9y7TBvnYcHyDQyY8KJBId5CZrFlCtxmHPBCDNpN909Nyl3YtDLhcN+2 YzJikcDS+mwuZRmFUXEe8PvlC0koVuG9ksuQNSO2Ah9/4OImDYlORNLe7AQk1D/V zjECMOiz3B5GTASF1dQQKkpBtuXOdooQthNDo0HtqnQIkRM8te8I4I4=

    Plugin Author Meitar

    (@meitar)

    8 years, 11 months ago

    Sigh. Quoting myself from earlier:

    It would help if you provided some technical details about the problem, rather than just a description that it occurs. For instance: a screenshot of what it looks like in Outlook, the raw source of the email sent from the plugin and then the raw source of the email received in Outlook, the public S/MIME cert to which you are encrypting, and so on.

    I don’t have time to do this with you piecemeal. You can file a bug report if you want. Please be sure you read How to Write a Good Bug Report before you do, if you file one.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Decrypting S/MIME messages using Outlook 2013’ is closed to new replies.