Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

S/MIME Signing and Encryption

#3384

I do have several certificates stored in my keychain. For some reason or other one of the certificates is not accepted anymore ( S/MIME: Failed to sign the message, Failed to encrypt the message) although it worked in the pas. All other certificates are ok. Using the same email address with Apple Mail works.

How can I check what causes the problem?

Thanks
Rober

Reported by Robert · August 21st, 2024 @ 10:14 AM

State: new
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny

    First, try updating to the latest test release: https://updates.mailmate-app.com/archives/MailMate_r6062.tbz

    Depending on the revision you are using now, you might get a better error message in the composer window which can point us in the right direction.

    August 23rd, 2024 @ 11:58 AM

  2. Robert
    Robert

    I went from 5973 to 6062.
    The message stays the same. Since I did not include the details when I opened the call here they are:

    S/MIME: Failed to sign the message
    Log S/MIME sign
    Sender robert@somedomain.xy
    Suggestion Verify that you have the certificate necessary to sign the message.

    I do have the necessary certificate in my keychain so I am a bit puzzled.

    August 27th, 2024 @ 12:47 PM

  3. benny
    benny

    Ok, try again after enabling this hidden preference (debug output isn't as good as it should be for S/MIME, but it could provide a bit more info):

    defaults write com.freron.MailMate MmDebugSecurity -bool YES
    

    Make sure the certificate is valid and trusted.

    August 28th, 2024 @ 02:44 PM

  4. Robert
    Robert

    Did that. I would have expected that there will be some output in /tmp but there is no /tmp/*mailmate* debug file present.

    August 29th, 2024 @ 08:30 AM

  5. benny
    benny

    No, the additional output should be in the same place as before. Just expand the “Failed to sign the message” error message.

    August 29th, 2024 @ 08:31 AM

  6. Robert
    Robert

    ok. Now I see it has changed ...

    Log S/MIME sign
    Searching for certificate of identity with address “robert@somedomain.xy” for signing
    Searching default keychain
    Looking for candidates (robert@somedomain.xy)
    Found 3 candidate(s)
    Searching all keychains
    Looking for candidates (robert@somedomain.xy)
    Found 3 candidate(s)
    Sender robert@somedomain.xy
    Suggestion Verify that you have the certificate necessary to sign the message.

    Hmm, my keychain only shows one (valid and trusted) certificate for that email address.

    August 29th, 2024 @ 10:50 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.