Skip to main content
WisMail

Let's Encrypt for a Mail Server

Published 2026-11-20

A mail server with a self-signed certificate still encrypts traffic, but Outlook, phones and many apps keep warning or refuse to connect. A free Let's Encrypt certificate fixes that.

Which names need a certificate

  • mail.example.com: the name you enter in mail apps (IMAP, SMTP, webmail).
  • autodiscover.example.com: if you use Outlook or devices that discover settings by themselves (DNS guide).

One certificate can hold both names.

Requirements for http-01

Let's Encrypt confirms you control a name by requesting http://name/.well-known/acme-challenge/... on port 80. So:

  1. Every name must resolve to the server's public IP.
  2. Port 80 must be open from the internet to the server (firewall, NAT).
  3. Nothing else may occupy port 80.

WisMail requests certificates over ACME v2 from web administration and checks for renewals every day. Wildcard certificates (which need DNS-01 validation) are not supported.

Common problems

  • Port 80 blocked by a provider firewall: validation fails. Open the port and retry.
  • A wrong AAAA (IPv6) record: Let's Encrypt prefers IPv6 when it exists. Remove the AAAA record or make sure the server receives IPv6.
  • Rate limits: repeated attempts get you temporarily blocked; fix the problem before retrying.

Verify after installing

openssl s_client -connect mail.example.com:993 -servername mail.example.com </dev/null | openssl x509 -noout -issuer -dates
openssl s_client -starttls smtp -connect mail.example.com:587 -servername mail.example.com </dev/null | openssl x509 -noout -issuer -dates

The output shows Let's Encrypt as the issuer and an expiry about 90 days away. See also the SSL certificates feature page.

Related documentation

Try it on your own server for 30 days

Install the package, register the trial and test with real users and devices. No payment card needed.