retlas

Registered
Apr 6, 2013
3
0
1
cPanel Access Level
Root Administrator
Hi guys,

Need a little guidance here and I can't seem to find the answer...

I have multiple accounts setup in WHM and use them for hosting the websites as well as mail servers.

We have recently moved one of the sites to a hosted cart system (3dcart).

Their email system sucks so I still want to use my sever as a mail server.

I realize I have to have them change the MX record on their end, but how do I properly configure it within WHM & cPanel?

Thanks for your help!
 

mtindor

Well-Known Member
Sep 14, 2004
1,363
65
178
inside a catfish
cPanel Access Level
Root Administrator
In cPanel, you'll have a DNS zone for that domain. In the cPanel account (via /cpanel) go to Advanced DNS editor and:

1. if mail.domain.com exists as a CNAME, change it to an "A" record and set it to the IP address of your server
2. in /cpanel under MX Entry, make sure mail.domain.com is the MX entry and that you select Local so that cPanel knows its the responsible mailserver

Then make sure that wherever the true DNS records are handled (I'm guessing at the place where the website is hosted), that they have:

1. mail.domain.com A xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx the IP address of your server)
2. a proper MX record in place

@ IN MX 0 mail.domain.com.

or

domain.com. IN MX 0 mail.domain.com.

I guess I should have asked first -- where is DNS handled? On your server or on a remote server? If on a remote server, the instructions above are correct [if I've made any sense].

M
 

retlas

Registered
Apr 6, 2013
3
0
1
cPanel Access Level
Root Administrator
Thank you.

Should I use the IP of the server or dedicate an IP address to the cPanel account for SSL mail?

Will SSL mail work on the already secure IP address of the server?
 

mtindor

Well-Known Member
Sep 14, 2004
1,363
65
178
inside a catfish
cPanel Access Level
Root Administrator
You can dedicate an IP if you want, but that seems like a pain to me. If you have an SSL tied to your main hostname, all of your clients phones and email clients can use it. Sure, they get a certificate warning, but all tehy have to do is accept it once and then forget it. I've never had customer complain that they had to accept the SSL security warning. On their phones it usually configures so easily that they don't even realize that they are being asked to confirm an SSL security warning [or they don't get one at all].

It's up to you. If your customers pay you good money and you feel you want to do something nice for them, then great -- set up SSL on a specific IP for them. Otherwise, just have them share the SSL on the main IP (if you have one, tied to the main hostname of your server).

Oh I didn't see your last question -- sure it will, but depending upon the email client, it might throw up an SSL warning letting your client know that the SSL hostname doesn't match the hostname of the server they are connecting to. All they have to do is accept it anyway. I've never had a customer complain about using that method, and it's easier all around.

M