📧
blog.cat.ssl

SSL for mail.domain.uz: Fixing the Outlook Certificate Warning

21.11.2026
← All articles

Many people who connect company mail to Outlook see the same thing: every time the program starts, a security certificate warning appears, saying the name on the certificate does not match the server. Staff click Yes and carry on, but the window is back the next day. The warning does not mean mail is broken, yet ignoring it is not the right answer either. This article explains why it appears, how to check it and how to get a proper certificate for a name like mail.example.uz.

What the warning actually means

When a mail client connects over IMAP, POP3 or SMTP, the server presents its SSL certificate. Outlook compares the names in that certificate with the server address in your settings. If you typed mail.example.uz but the server presents a certificate for another name, such as its own technical hostname, Outlook reports a mismatch. Encryption still works, but the client cannot confirm it is talking to the right server. This is common on shared mail servers hosting hundreds of domains: unless the server presents a separate certificate for each mail. name, it falls back to its main hostname and every customer sees the warning.

Why clicking Yes is not a fix

Training staff to dismiss certificate prompts is dangerous. The day a real interception attempt happens, they will click Yes just as automatically. Some mobile mail apps and newer Outlook versions may also refuse a mismatched certificate outright, so fix the root cause.

Check which certificate the server presents

The -servername flag matters: it tells the server via SNI which name you want, and a correctly configured server returns the matching certificate.

dig A mail.example.uz +short
dig MX example.uz +short

openssl s_client -connect mail.example.uz:993 -servername mail.example.uz </dev/null 2>/dev/null \
  | openssl x509 -noout -subject -ext subjectAltName -dates

openssl s_client -starttls smtp -connect mail.example.uz:587 -servername mail.example.uz </dev/null

If subjectAltName does not contain DNS:mail.example.uz, that is your problem.

Fix one: use the provider's server name

The quickest reliable fix is to enter the server name your hosting provider gives you instead of mail.example.uz. The provider already has an auto-renewing certificate for it, so the warning disappears immediately, and your address stays info@example.uz. sayt.uz customers can find the correct mail server name in the cabinet or through support. The downside is updating every staff device, which takes minutes in a small team but needs planning in a large one.

Fix two: a dedicated certificate for mail.example.uz

If branding matters, the mail server must present its own certificate for mail.example.uz. The A record must point to the mail server, and the CA must be able to validate the name. If the website lives elsewhere or port 80 is closed, DNS-01 validation is easiest because it only checks a TXT record and never touches the site's A record.

certbot certonly --manual --preferred-challenges dns -d mail.example.uz
dig TXT _acme-challenge.mail.example.uz +short

Manual DNS-01 needs a new TXT record at every renewal, so permanent setups should use a client automated through a DNS API. On your own server, attach the certificate via SNI. In Dovecot 2.3 (parameter names changed in 2.4, check the docs):

local_name mail.example.uz {
  ssl_cert = </etc/letsencrypt/live/mail.example.uz/fullchain.pem
  ssl_key = </etc/letsencrypt/live/mail.example.uz/privkey.pem
}

Do the same for SMTP in Exim or Postfix, or Outlook will stay quiet on IMAP but keep warning when sending.

Autodiscover, the overlooked source

Outlook also queries autodiscover.example.uz and https://example.uz/autodiscover/autodiscover.xml. If the website certificate does not cover those names, the warning may come from there instead. Read the name in the dialog: if it starts with autodiscover, the mail server is not the culprit, and removing that record or giving it a valid certificate helps.

Example: the daily pop-up at a clinic

A private clinic in Samarkand uses mail on misol.uz for twelve staff. The website is on a site builder and mail is on a hosting server. Outlook used mail.misol.uz and showed a certificate warning every morning. The check showed the name pointed to the right server, which only had a certificate for its own hostname. The admin issued a certificate for mail.misol.uz via DNS-01 and attached it to the mail server without touching the website records. The pop-up stopped and nobody had to reconfigure anything. Remember that Let's Encrypt certificates expire after 90 days, and Dovecot and the SMTP service must be reloaded after renewal to pick up the new file.

Related articles

⏳ Let's Encrypt Rate Limits: Fixing "too many certificates" 📜 Certificate Transparency: How Public Logs of SSL Certificates Work 🏢 SSL for internal (intranet) sites: how to secure office systems 🔐 What Is Perfect Forward Secrecy and How It Protects Your Site
🌐 Language
🇺🇿 O⁠'zbek 🇺🇿 Özbek (yangi) 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓