• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved my emails from my domains are tagged as spam by gmail

drusixtynine

Basic Pleskian
Hi there,
I know this is a recurring problem, but I can not find a solution in all the posts I've been seeing
I have a VPS with plesk 12.0.8 installed on it and I am hosting multiple domains on it
I have properly configured SPF in my domain and when I send an email to a gmail address, it is not received in the inbox but in the spam folder.
I have tested emails with mail-tester.com and my score is 9/10 because I do not have DKIM configured, as this version of plesk does not support it (and I don't want to upgrade with risking that the upgrade goes wrong and my customers get stuck)
As you can see in the email original header, SPF and dmarc are passing
mail-tester.com is having a warning with my reverse DNS as the IP reverse DNS record sends to mymaindomain.com and the SMTP HELO message provides myVPSaddress.ovh.net

I've hidden domain names, VPS name and so on for privacy of my customer and so on, sorry for that

So here I am, stuck, not knowing what to do more
Please, any help would be appreciated

Aziz

Code:
Delivered-To: [email protected]
Received: by 10.200.51.163 with SMTP id c32csp6843983qtb;
        Wed, 6 Dec 2017 03:49:00 -0800 (PST)
X-Google-Smtp-Source: AGs4zMYjB0fl09qdgN1xu3Psi0Xbu6ADhmLInXnoVKqgrDtqK7oWt+WVI0Va4Rwz+SpZwViVFee7
X-Received: by 10.28.45.151 with SMTP id t145mr7637295wmt.108.1512560940870;
        Wed, 06 Dec 2017 03:49:00 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1512560940; cv=none;
        d=google.com; s=arc-20160816;
        b=wxrxOk3zE6nkqqkPzEW0HXPM+z/J7y8eptLRlCSLbV6U5fUj7qp2o1t3ScrAElECBY
         P+rqsKFJ5eGK7dPVqdPE9ernTTsrtA60BeD0jP6OSg1Haa/AHfPNjzx8yneu+3RvRqIj
         JKy7mSNU4hlXCHSTSRHsOaUBwf94mX2ZvG3cyf9K5QqIT2dvZ/Kb7milGjQ9Hs9HWf1t
         GzkSS8/uCbj4jrSr+HkdAsQyYzpmGM6ySaDFziKP+Jy4yj6aNVs3Q5TcxiOAdidpvuwd
         I9A3f4ikEpfCGZx5P9qa0iCbqWDkcAhHeqabY5STZlYusEMOzSt4nX7YJ3yw5C4Zt6ns
         e7gw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=user-agent:message-id:subject:to:from:date
         :content-transfer-encoding:mime-version:arc-authentication-results;
        bh=+JdJnpAhwQC6DVUV9iO78NR2SWlur3o996ynao9UdaQ=;
        b=StMsa0az6NzXSkfE0OlaAWi0+7B4vyorvWdFZ3of87OjfLNBvJ63Syz9nMQSr6rLfS
         Lc37LAoxD2x0IcAgBB/yLuS8BQ510xCZhXKTclDUJHiDemy+lOQjKrfMwn7Kba8V70q3
         f9bWXOx5F/fb64P+JrqeCY3OQsj1mmcIz4ghpUaqiz/uZ4h+51UxlfWnfduxF0dJZRMt
         eUd5pNCM3Bb+kyeMzcKAHs7+57gcuzRXgEWhDEy9aZR7x7MaMDPrGylfg9BuBNwoMdsn
         l9d2UeeiyY5pIblepJZRifPYN8Zi07F7bDmJJOqNVOLsBnnwTSqPjh9WCmcLHT9un9qw
         Xo9g==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mydomain.com
Return-Path: <[email protected]>
Received: from myVPS.ovh.net ([2001:41d0:52:800::12])
        by mx.google.com with ESMTPS id z56si1996310wrz.517.2017.12.06.03.49.00
        for <[email protected]>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 06 Dec 2017 03:49:00 -0800 (PST)
Received-SPF: pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) client-ip=2001:41d0:52:800::12;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mydomain.com
Received: from webmail.mydomain.com (localhost [IPv6:::1]) by myvps.ovh.net (Postfix) with ESMTPA id B7B7F260369E for <[email protected]>; Wed,
  6 Dec 2017 12:48:59 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 06 Dec 2017 12:48:59 +0100
From: [email protected]
To: [email protected]
Subject: test 12:48
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.1.4
 
Hi there,
I know this is a recurring problem, but I can not find a solution in all the posts I've been seeing
I have a VPS with plesk 12.0.8 installed on it and I am hosting multiple domains on it
I have properly configured SPF in my domain and when I send an email to a gmail address, it is not received in the inbox but in the spam folder.
I have tested emails with mail-tester.com and my score is 9/10 because I do not have DKIM configured, as this version of plesk does not support it (and I don't want to upgrade with risking that the upgrade goes wrong and my customers get stuck)
As you can see in the email original header, SPF and dmarc are passing
mail-tester.com is having a warning with my reverse DNS as the IP reverse DNS record sends to mymaindomain.com and the SMTP HELO message provides myVPSaddress.ovh.net

I've hidden domain names, VPS name and so on for privacy of my customer and so on, sorry for that

So here I am, stuck, not knowing what to do more
Please, any help would be appreciated

Aziz

Code:
Delivered-To: [email protected]
Received: by 10.200.51.163 with SMTP id c32csp6843983qtb;
        Wed, 6 Dec 2017 03:49:00 -0800 (PST)
X-Google-Smtp-Source: AGs4zMYjB0fl09qdgN1xu3Psi0Xbu6ADhmLInXnoVKqgrDtqK7oWt+WVI0Va4Rwz+SpZwViVFee7
X-Received: by 10.28.45.151 with SMTP id t145mr7637295wmt.108.1512560940870;
        Wed, 06 Dec 2017 03:49:00 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1512560940; cv=none;
        d=google.com; s=arc-20160816;
        b=wxrxOk3zE6nkqqkPzEW0HXPM+z/J7y8eptLRlCSLbV6U5fUj7qp2o1t3ScrAElECBY
         P+rqsKFJ5eGK7dPVqdPE9ernTTsrtA60BeD0jP6OSg1Haa/AHfPNjzx8yneu+3RvRqIj
         JKy7mSNU4hlXCHSTSRHsOaUBwf94mX2ZvG3cyf9K5QqIT2dvZ/Kb7milGjQ9Hs9HWf1t
         GzkSS8/uCbj4jrSr+HkdAsQyYzpmGM6ySaDFziKP+Jy4yj6aNVs3Q5TcxiOAdidpvuwd
         I9A3f4ikEpfCGZx5P9qa0iCbqWDkcAhHeqabY5STZlYusEMOzSt4nX7YJ3yw5C4Zt6ns
         e7gw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=user-agent:message-id:subject:to:from:date
         :content-transfer-encoding:mime-version:arc-authentication-results;
        bh=+JdJnpAhwQC6DVUV9iO78NR2SWlur3o996ynao9UdaQ=;
        b=StMsa0az6NzXSkfE0OlaAWi0+7B4vyorvWdFZ3of87OjfLNBvJ63Syz9nMQSr6rLfS
         Lc37LAoxD2x0IcAgBB/yLuS8BQ510xCZhXKTclDUJHiDemy+lOQjKrfMwn7Kba8V70q3
         f9bWXOx5F/fb64P+JrqeCY3OQsj1mmcIz4ghpUaqiz/uZ4h+51UxlfWnfduxF0dJZRMt
         eUd5pNCM3Bb+kyeMzcKAHs7+57gcuzRXgEWhDEy9aZR7x7MaMDPrGylfg9BuBNwoMdsn
         l9d2UeeiyY5pIblepJZRifPYN8Zi07F7bDmJJOqNVOLsBnnwTSqPjh9WCmcLHT9un9qw
         Xo9g==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mydomain.com
Return-Path: <[email protected]>
Received: from myVPS.ovh.net ([2001:41d0:52:800::12])
        by mx.google.com with ESMTPS id z56si1996310wrz.517.2017.12.06.03.49.00
        for <[email protected]>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 06 Dec 2017 03:49:00 -0800 (PST)
Received-SPF: pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) client-ip=2001:41d0:52:800::12;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 2001:41d0:52:800::12 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mydomain.com
Received: from webmail.mydomain.com (localhost [IPv6:::1]) by myvps.ovh.net (Postfix) with ESMTPA id B7B7F260369E for <[email protected]>; Wed,
  6 Dec 2017 12:48:59 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Wed, 06 Dec 2017 12:48:59 +0100
From: [email protected]
To: [email protected]
Subject: test 12:48
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.1.4

Hello @drusixtynine ,

You have to set the rDNS on your vps IP with the vps hostname , you can edit this option in your OVH manager.
But even if you use a proper SPF, DKIM , DMARC and score 10/10 on mail-tester, there is no way to make sure your email with not be tagged as spam by gmail (and other services like outlook.com ).
OVH VPS IP are often blacklisted for spam, and sometimes a full IP block is blacklisted.
 
Hi Virtubox and thank you for answering,
as I said, on my OVH manager I have already configured a reverse DNS from my IP address pointing to myMainDomain.com which is different from myVPS.ovh.net and which triggers a warning on mail-tester.com as follows

Your IP address xx.xx.xx.xx is associated with the domain mail.mymaindomain.com
Nevertheless your message appears to be sent from myvps.ovh.net.

You may want to change your pointer (PTR type) DNS record and the host name of your server to the same value.



Here are the tested values for this check:
  • IP: xx.xx.xx.xx
  • HELO: myvps.ovh.net
  • rDNS: mail.mymaindomain
 
Hi Virtubox and thank you for answering,
as I said, on my OVH manager I have already configured a reverse DNS from my IP address pointing to myMainDomain.com which is different from myVPS.ovh.net and which triggers a warning on mail-tester.com as follows

Your IP address xx.xx.xx.xx is associated with the domain mail.mymaindomain.com
Nevertheless your message appears to be sent from myvps.ovh.net.

You may want to change your pointer (PTR type) DNS record and the host name of your server to the same value.



Here are the tested values for this check:
  • IP: xx.xx.xx.xx
  • HELO: myvps.ovh.net
  • rDNS: mail.mymaindomain

The rDNS should be the server hostname and a FQDN (fully qualified domain name). So you have to replace it with vpsXXX.ovh.net.
Via ssh to check your hostname you can use :

Code:
hostname   ## to see the  server hostname
hostname   -f ## to see the FQDN
 
Hi again Virtubox and thx again for answering back,
both commands return my VPS name, thus vpsXXX.ovh.net
OVH manager doesn't allow me to change the reverse DNS to ovh.net domain, it says 'Reverse cannot be in ovh.net domain'
Is there a way to change it through ssh?
 
Hi again Virtubox and thx again for answering back,
both commands return my VPS name, thus vpsXXX.ovh.net
OVH manager doesn't allow me to change the reverse DNS to ovh.net domain, it says 'Reverse cannot be in ovh.net domain'
Is there a way to change it through ssh?

In this case, the easiest is to change the hostname, and to use one of your subdomains, like vps.yourdomain.tld.
It will require to add a A records to the VPS IP, and then you will be able to change the rDNS with your new hostname.

Hostname modification require to reboot the vps.

The best documentation about hostname configuration for a mail server is available here :
debian/ubuntu : Install iRedMail on Debian or Ubuntu Linux
centos : Install iRedMail on Red Hat Enterprise Linux, CentOS
 
changing the host name doesn't change anything? except that the address for plesk will change... nothing else?
I mean, is it safe to change it?
 
changing the host name doesn't change anything? except that the address for plesk will change... nothing else?
I mean, is it safe to change it?

You will probably have to update your domains DNS settings to apply the new domain in the SPF directive, but it should not impact the address used to access to plesk because you can access it from any domain pointed to your server :8443.

Additionaly it will provide you (I'm not sure for Plesk 12.0.8 ,because it's pretty old) the ability to secure the Plesk interface with letsencrypt , as ovh.net domain cannot be used due to the amount of requests.
 
yes u r right about the plesk address
also, do you think it could address my spam problem, at least partially to have the host name and the rDNS aligned?
 
yes u r right about the plesk address
also, do you think it could address my spam problem, at least partially to have the host name and the rDNS aligned?

The most part of antispam system will not accept an email from a server with an incorrect rDNS.
Because it's the only proof (without DKIM) to see if a emails is sent from your server.
 
hi there, I finally managed to rename my host and it looks that it got way better with gmail, I'm still checking though. Thank you very much for that
After that I tried to install a certificate from let's encrypt through certbot and it got my apache down and I had to comment some lines in my apache config files and now I have a weird message in my plesk
Can you help me with that here or should I create another post?
 
Back
Top