Are you really sure? I mean, do you know where can i find information about this topic? As i planned to operate that way, buying cheap ssl certs for multiple domains/subdomains i would like to be sure before discarding that procedure.
Thanks a lot!! Sent from my Android mobile, excuse the brevity. On Mar 26, 2014 9:28 PM, "Viktor Dukhovni" <postfix-us...@dukhovni.org> wrote: > On Wed, Mar 26, 2014 at 09:13:58PM +0100, Pau Peris wrote: > > > Common Name (CN) we.webeloping.es > > > > X509v3 Subject Alternative Name: > > DNS:webeloping.com, > > DNS:demo.webeloping.com, > > DNS:imap.webeloping.com, > > DNS:mail.webeloping.com, > > DNS:smtp.webeloping.com, > > DNS:test.webeloping.com, > > DNS:we.webeloping.com, > > DNS:*.webeloping.com > > DNS:webeloping.es, > > DNS:*.webeloping.es, > > DNS:demo.webeloping.es, > > DNS:imap.webeloping.es, > > DNS:mail.webeloping.es, > > DNS:smtp.webeloping.es, > > DNS:test.webeloping.es, > > DNS:we.webeloping.es, > > > > By "access my server from <some-domain>" I mean: > > Configuring a desktop email client to access IMAP and SMTP servers. > > s/from/as/ > > > we.webeloping.es and we.webeloping.es respectively work like a charm, > while > > using imap.webeloping.es and smtp.webeloping.es makes the email client > show > > the typical SSL warning complaining about the host not being the common > name > > Well, now you know what not to do. :-( The mail client wants the server > name in the CN. > > -- > Viktor. >
