<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 10 March 2018 at 05:58 "@lbutlr" <
<a href="mailto:kremels@kreme.com">kremels@kreme.com</a>> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
On 2018-02-25 (09:31 MST), David Favor <
<a href="mailto:david@davidfavor.com">david@davidfavor.com</a>> wrote:
</div>
<blockquote type="cite">
<div>
}
</div>
<div>
local_name imap.cydec.com {
</div>
<div>
ssl_cert = </etc/letsencrypt/live/imap.cydec.com/fullchain.pem
</div>
<div>
ssl_key = # hidden, use -P to show it
</div>
<div>
}
</div>
</blockquote>
<div>
Doesn't this still require a default t(top level) cert besides the one specified for local_name?
</div>
<div>
<br>
</div>
<div>
Also, is there any reason to use local_name if your local name matches your server? the point is to be able to provide a cert for example.org when your domain is example.com, right?
</div>
<div>
<br>
</div>
<div>
--
</div>
<div>
Don't congratulate yourself too much, or berate yourself either. You
</div>
<div>
choices are half chance; so are everybody else's.
</div>
<div>
<br>
</div>
</blockquote>
<div>
<br>
</div>
<div>
A default cert is always needed. If you have only one certificate don't use local_name.
</div>
<div class="io-ox-signature">
---
<br>Aki Tuomi
</div>
</body>
</html>