Issue with Installi...
Clear all

[Solved] Issue with Installing mailboxd SSL certificates - Error in Zimbra Setup

3 Posts
2 Users
Joined: 9 months ago
Posts: 4
Topic starter  

Hello everyone,

I'm facing an issue while installing Zimbra Collaboration Suite (ZCS) on my Ubuntu 20.04 server. I downloaded the file "zcs-9.0.0_OSE_UBUNTU20_latest-zextras.tgz" and followed the installation process. However, during the installation, I encountered an error related to "Installing mailboxd SSL certificates," which unfortunately failed.

Upon further investigation in the "/tmp/zmsetup.log" file, I found the following error message:

ERROR: openssl pkcs12 export to '/opt/zimbra/ssl/zimbra/jetty.pkcs12' failed(1):
Error creating PKCS12 MAC; no PKCS12KDF support?
Use -nomac if MAC not required and PKCS12KDF support not available.
80E2B76A657F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:373:Global default library context, Algorithm (PKCS12KDF : 192), Properties (<null>)
80E2B76A657F0000:error:1180006B:PKCS12 routines:pkcs12_gen_mac:key gen error:crypto/pkcs12/p12_mutl.c:147:
80E2B76A657F0000:error:1180006D:PKCS12 routines:PKCS12_set_mac:mac generation error:crypto/pkcs12/p12_mutl.c:220:
Sun Jul 30 17:35:27 2023 failed.

I'm not sure what's causing this error or how to resolve it. It seems to be related to an issue with PKCS12KDF support, but I'm not familiar with how to address it.

If anyone has encountered this problem before or has any insights on how to fix it, I would greatly appreciate your help. I'm eager to get Zimbra up and running on my server, and any guidance you can provide would be incredibly valuable.

Thank you in advance for your time and assistance!

Best regards,
Utsav Maharjan

Joined: 3 years ago
Posts: 153



If you search for "nomac" in the forum, you'll find a post (I think by anahuac) with a solution/workaround.

Joined: 9 months ago
Posts: 4
Topic starter  

@stefanodavid I want to express my sincere gratitude for the useful information you provided. I'm happy to report that the problem has been rectified thanks to the workaround offered by @anahuac.

anahuac reacted