<div>
Hmmm, so attaching a certificate to the mail gateway of *.domain.com would allow it to respond to TLS/SSH conversations for smail.domain.com and/or smail2.domain.com and/or smail3.domain.com without a certificate error? &nbsp;Just making sure before I send out the CSR. &nbsp;Also, in Apache, how do you do a CSR for a wildcard cert?<br />
<br />
Thanks
</div>


Hmmm, so attaching a certificate to the mail gateway of *.domain.com would allow it to respond to TLS/SSH conversations for smail.domain.com and/or smail2.domain.com and/or smail3.domain.com without a certificate error?  Just making sure before I send out the CSR.  Also, in Apache, how do you do a CSR for a wildcard cert?

Thanks

<div>
<div class="content wysiwyg-content">
I'll be deploying a new email gateway named “smail.domain.com”. &nbsp;It will be accessible from 3 different public IPs. &nbsp;So, MX records will list smail, smail2, and smail3 in descending preference. &nbsp;I would like to deploy it with an SSL cert for all 3 names, but I am fairly certain that you cannot deploy a host with 3 SSL certs. &nbsp;My thought is to use a wild-card SSL cert, but will this even work? &nbsp;All advice is appreciated.<br />
<br />
As well, for a host handling TLS, HTTPS, and SMIME, are there any particulars I need for the cert?
</div>
</div>


I'll be deploying a new email gateway named “smail.domain.com”.  It will be accessible from 3 different public IPs.  So, MX records will list smail, smail2, and smail3 in descending preference.  I would like to deploy it with an SSL cert for all 3 names, but I am fairly certain that you cannot deploy a host with 3 SSL certs.  My thought is to use a wild-card SSL cert, but will this even work?  All advice is appreciated.

As well, for a host handling TLS, HTTPS, and SMIME, are there any particulars I need for the cert?

SSL Certificates for eMail Gateway

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.