# Zimbra Mail Server **URL:** \ **Category:** Server\ **Created:** [November 9, 2015, 2:28pm UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389 "2015-11-09T14:28:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![NorD](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@NorD](https://community.letsencrypt.org/u/NorD)\ **Post date:** [November 9, 2015, 2:28pm UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/1 "2015-11-09T14:28:57Z")
Hi, How does automatic script with Zimbra ? ---
**Author:** ![kasi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kasi/32/2485_2.png) [@kasi](https://community.letsencrypt.org/u/kasi)\ **Post date:** [December 3, 2015, 6:37pm UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/2 "2015-12-03T18:37:43Z")
I will be interested also to be able to use Let’s Encrypt with a Zimbra server :). ---
**Author:** ![kasi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kasi/32/2485_2.png) [@kasi](https://community.letsencrypt.org/u/kasi)\ **Post date:** [December 7, 2015, 7:27am UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/3 "2015-12-07T07:27:51Z")
[https://wiki.zimbra.com/wiki/Installing\_a\_LetsEncrypt\_SSL\_Certificate](https://wiki.zimbra.com/wiki/Installing_a_LetsEncrypt_SSL_Certificate) ---
**Author:** ![NorD](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@NorD](https://community.letsencrypt.org/u/NorD)\ **Post date:** [December 7, 2015, 8:33am UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/4 "2015-12-07T08:33:50Z")
Thank you, but Failed authorization procedure. [mx.sushi.ru](http://mx.sushi.ru) (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client for DV :: Failed to connect to host for DVSNI challenge IMPORTANT NOTES: - If you lose your account credentials, you can recover through e-mails sent to [postmaster@sushi.ru](mailto:postmaster@sushi.ru). - The following ‘urn:acme:error:connection’ errors were reported by the server: - Your account credentials have been saved in your Let’s Encrypt configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Let’s Encrypt so making regular backups of this folder is ideal. ---
**Author:** ![janadel](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@janadel](https://community.letsencrypt.org/u/janadel)\ **Post date:** [January 7, 2016, 4:33pm UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/5 "2016-01-07T16:33:42Z")
Same problem here.Did you find a solution ? Thanks ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [January 7, 2016, 5:03pm UTC](https://community.letsencrypt.org/t/zimbra-mail-server/3389/6 "2016-01-07T17:03:45Z")
Well, in the case of @NorD the hostname `mx.sushi.ru` doesn’t even have an IP address associated with it. So **nothing** can connect to it. I’m wondering if e-mails to the domain `sushi.ru` even arrive? Anyway, just stating “same problem here” isn’t getting you anywhere I’m afraid. The Let’s Encrypt ACME server has multiple challenge systems and currently it uses the `http-01` and/or `tls-sni-01` challenge for the “live” server. This means there has to be a HTTP or HTTPS (respectively) listening on port 80 and/or 443 on the hostname(s)/(sub)domain(s) you want a certificate for. At the moment there’s also a DNS challenge system being developed (so no need for accessibility on port 80 and/or 443 required), but this is currently in the “staging” server only (which doesn’t generate “real” trusted certificates you can use). Also, it’s not very well documentated as far as I know and I’ve got no clue if it’s implemented in the official client at all. If your mailserver _also_ runs a webserver, then you possibly could use that one. Depends on how you call your mailserver. You probably don’t have a virtualhost called `mx.yourdomain.tld` on your webserver. If your mailserver doesn’t come with a webserver, you could use the [standalone plugin](http://letsencrypt.readthedocs.org/en/latest/using.html#standalone), which acts as its own temporary webserver. But ofcourse, the server should be reachable on port 80 and 443 from the internet for this to work.