# Simple Guide: Using Lets Encrypt SSL certs with Dovecot

**URL:** <https://community.letsencrypt.org/t/simple-guide-using-lets-encrypt-ssl-certs-with-dovecot/2921>\
**Category:** Server\
**Created:** [November 4, 2015, 4:41pm UTC](https://community.letsencrypt.org/t/simple-guide-using-lets-encrypt-ssl-certs-with-dovecot/2921 "2015-11-04T16:41:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jbvignaud](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@jbvignaud](https://community.letsencrypt.org/u/jbvignaud)\
**Post date:** [November 5, 2015, 9:59am UTC](https://community.letsencrypt.org/t/simple-guide-using-lets-encrypt-ssl-certs-with-dovecot/2921/2 "2015-11-05T09:59:38Z")

</div>

Dovecot also supports SNI, so you can put a couple of cert / key for each domain you hosts.

I use this kind of config myself:

```
ssl_cert = </path_to/default_crt.pem
ssl_key = </path_to/default_key.pem

```

!include conf.d/dovecot-crt\*.conf

and for example dovecot-crt\_imap\_domain1\_td.conf like this:

```
local_name imap.domain1.td {
  ssl_cert = </path_to/imap.domain1.td_crt.pem
  ssl_key = </path_to/imap.domain1.td_key.pem
}

 dovecot-crt_imap_domain2_td.conf:

local_name imap.domain2.td {
  ssl_cert = </path_to/imap.domain2.td_crt.pem
  ssl_key = </path_to/imap.domain2.td_key.pem
}

```

This way thunderbird can request the correct certificate, and this allows user to connect / configure accounts using [imap.domain1.td](http://imap.domain1.td) or [imap.domain2.td](http://imap.domain2.td) depending on the email address without receiving cert errors.

---

_[View the full topic](https://community.letsencrypt.org/t/simple-guide-using-lets-encrypt-ssl-certs-with-dovecot/2921)._