Email Server on CentOS 7.x with Sentora CP?

Posted March 13, 2017 6.1k views
CentOSEmailDNSControl Panels

I want to set up a personal email server in my droplet having sentora control panel!

I have used iredmail, but no luck it causing problem with sentora CP.

Tried with postfix and dovecot, still no luck it only send mail and can’t connect to a desktop email client like outlook and Thunderbird.

I want to make available my email account to send and receive mail via outlook or Thunderbird mail client using my CENTOS server.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer


When it comes to setting up a fully functional, working e-mail server, ideally you need to set it up on it’s own Droplet/Server – independent of your web server. There’s a lot that goes in to running a mail server, specifically ensuring that SPF, DKIM and potentially DMARC are working as intended as those are three things that are going to keep your e-mail out of the junk/spam folders (without them, mail is going to end up in junk/spam).

If you’re dead-set on running your own mail server, I’d take a look at MailCow. It’s relatively easy to set up and use.

  • @jtittle thanks for the help!
    will work on that with new droplet but at my current droplet i’ve installed sentora panel which i think causing the problem but its fixed as:

    First point the the to droplet IP as a A record and same doamin as a MX record
    1. Editing vi /etc/postfix/ and adding submission inet n - n - - smtpd code after smtp inet n -n –smtpd

    2. restart the postfix and server

    • @techroadians

      No problem. The reason I mention MailCow, and recommend running a mail server on a server that’s independent of your web server is also due to PTR records (Reverse DNS).

      Some providers will reject mail or immediately flag it as spam/junk when your PTR doesn’t validate. With DigitalOcean, your PTR is set as whatever you name your Droplet to and this can only be changed by changing the name of your Droplet (from the control panel).

      So if you named your Droplet, for example, web01 (i.e. without a domain name), then web01 is the PTR record for that Droplet which actually won’t resolve properly (there’s not a valid association with a domain).

      On the other hand, if we named it and there’s a valid A entry for web01 to associate your domain with, then the PTR record is valid.

      How this applies to a mail server is similar.

      If we have and we setup an A or CNAME entry for for use by our mail server, doesn’t have a valid PTR record, only does, thus reverse DNS lookups will fail.

      Like I said above, there’s a lot that goes in to managing a mail server, much of which most control panel software developers/designers fail to mention or even handle.