Vesta Control Panel - Forum

Hi all

I love Vesta so far it has made life very easy for once. I only have one more issue to over come before I use it as my driver.

Any email I send from Roundcube is marked as Spam in ether Gmail or Outlook.com. From what I can tell all my settings are correct.

PTR is set correct back to my host. for example, abc.com (should this be set to mail.abc.com?) is set a PTR. DKIM and SPF are set automatically.

Can any one please advice ?

Same for me. No one answered in my thread too. I'm getting 100% in mailtest.
My previous mailserver got ~6-7 in mailtest, but I didn't have any problem with gmail, outlook and other providers. I don't know what's wrong with vesta config and I would be glad if someone wise in mailserver config check it.

To me, roundcube used php to send mail and that caused problems, I had to set it up so send via SMTP so that it wouldn't be marked as spam in some providers (see below).

I'd recommend setting up a couple of free accounts with them in order to test deliverability on their servers, as even mail-tester.com can give you an idea on what's wrong, Gmail and Outlook use their own spam toolkits.

Also check that your ip address or subnet is clean, as outlook seems to be banning entire subnets very easily (you usually get a rejected message from them in that case). I had to change my mail server ip to another one, as the first one I had was flagged in Outlook because of it's subnet.

In order to change roundcube to not to send via php's mail function, you can change the following values in /etc/roundcube/config.inc.php in debian ( main.inc.php in centos maybe?):

$rcmail_config['smtp_server'] = 'localhost';
$rcmail_config['smtp_user'] = '%u';
$rcmail_config['smtp_pass'] = '%p';

codibit wrote: ↑

Tue Dec 11, 2018 2:02 pm

To me, roundcube used php to send mail and that caused problems, I had to set it up so send via SMTP so that it wouldn't be marked as spam in some providers (see below).

I'd recommend setting up a couple of free accounts with them in order to test deliverability on their servers, as even mail-tester.com can give you an idea on what's wrong, Gmail and Outlook use their own spam toolkits.

Also check that your ip address or subnet is clean, as outlook seems to be banning entire subnets very easily (you usually get a rejected message from them in that case). I had to change my mail server ip to another one, as the first one I had was flagged in Outlook because of it's subnet.

In order to change roundcube to not to send via php's mail function, you can change the following values in /etc/roundcube/config.inc.php in debian ( main.inc.php in centos maybe?):

$rcmail_config['smtp_server'] = 'localhost';
$rcmail_config['smtp_user'] = '%u';
$rcmail_config['smtp_pass'] = '%p';

Did this solution work for anybody?

Thanks

I am not using vesta currently, however i have had this problem with other control panels.
My understanding is that the following issues often cause the problem...

1. if you use hostname.fqdn for the mx record value then it must match the mail server hostname.fqdn that is sending the mail and not mail.clientdomain.com

So if your server is not actually called mail.domain.com don't use "mail" in the mx record...use your actual Mail Server's own hostname.domain.com here

Example (if you are not using the ipaddress method for mxrecord)
if server is called server5
and wehbosting business/mail server domain is aaahosting.com
and a client on the server is adamsdomain.com

then dns mxrecord for adamsdomain.com would be...

adamsdomain.com MX record server5.aaahosting.com

2. All spf records (including those for client dns records) need to have the actual mail server hostname.fqdn that is sending emails for a client email domain...putting the clients own mail.domain.com will not work as that is not the name of the mail server sending emails on behalf of client domain.

3. Postfix can only handle one SSL certificate per Ipaddress. So copying numerous client SSL certs to postfix will just overwrite previous one each time you do it. That's brilliant for the most recent client...but useless for all of the others previous.

4. The next thing is whether to point mx record at a hostname.fqdn or at an ipaddress. Some say ipaddress because that reduces the number of dns lookups, but I often see host.fqdn

5. Also, you need to include _DMARC record in clients dns, otherwise a lot of email recipient programs will send to trash/spam

6. I havent ever needed DKIM but some use it...I havent found it replaces spf (but that might just be me and the way i implement DKIM?)

I think that due to a single ip address issue with postfix, one will probably almost always get the "untrusted SSL cert" warning in outlook when setting up client email apps...i seem to rarely not at least get that error. I for one would welcom any further ideas on how to fix this?

Finally, I have had no luck using XML auto config files for Outlook (or any other email client desktop pc and mobile apps).