Client setup: use box's MX or domain's MX

Help with Setup
#1

Good morning,

a newbie setup question for multiple domains (all handled my mailinabox’s DNS). I searched in the forum but could not find a definitive answer and I am afraid that a wrong setup may lead to blacklist etc.

Question: When setting up an email client to send/receive mail for MYDOMAIN.COM, I would want to use as IMAP/POP MAIL.MYDOMAIN.COM instead of using the server names of my Mailinabox.

Cna this be accoplised by creating a CNAME record or I am breaking something here?

Bottom line: can the mail/pop server names for a domain be aligned to the same domain name?

Thank you very much and best,

Dudi

#2

No, that is not an option. If you want to use mail.mydomain.com as the server name, then when you set the server up use mail.mydomain.com rather than box.mydomain.com.

But wait, you are talking about multiple domains, right? Mail-in-a-Box wasn’t really created to be concerned with vanity. Traditionally, mail servers served email for multiple domains, and people dis not worry about what the MX record was. The MX record was what it was. Then cPanel changed all of that.

My best suggestion to you is to use a neutral domain name for the mail server. Maybe something like dudiellomail.net.

Or, you can be the guinea pig. Try adding a email account for mail.domain.com for a few domains, then test. I know this works well for webmail access, but I imaging that it will fail miserably as the SSL certificate used by dovecot will be the main server certificate. So no, I don’t think you can actually do what you want with MiaB.

Bottom line: Probably not as dovecot will be using the server’s SSL certificate.

1 Like
#3

u can set an A record, but the certificate will not be valid. However, in this case, a paid multi domain SSL may be the solution.

1 Like
#4

I haven’t messed around with it, but doesn’t Let’s Encrypt support wildcard certificates?

#5

turn out postfix in mailinabox is only 3.3, SNI is supported only in 3.4, so may need to wait

#6

I’m having the same issue with a server migration.

letsencrypt supports multi-domain certificates - the old not-mailinabox server uses acme which handles multiple domains in it’s config. So there should be an equivalent change for mailinabox to use the same feature. (I haven’t been able to find it yet though).

#7

the dovecot side is easily solvable, it’s the postfix side, i’m not sure how to fix it

#8

Thanks Alento and all of you for the your answers, seems like this feature is not available out-of-the (mailina)box. Given the fact that it may not be good to play around with configurations, I will await for future update…and also file a suggestion.

Thanks guys

#9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.