• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue My Configurations Good but mail go to spam

Kais

New Pleskian
Hi Pleskers , Please I need your help

I already installed and configured a new vps from Contabo ,
I installed CentOS 7 (64bit) , next i install Plesk Obsidian
I added my domain but when it come to sending mails
the mails goes to spam even mail-tester result is 10/10

But I noticed that there is something stranger which is the mail source.
which is the 127.0.0.1 ip adress,

Code:
Received: from webmail.mega-dev.net (mail.mega-dev.net [127.0.0.1])
and
Code:
 spf=pass (sender IP is 127.0.0.1) [email protected] smtp.helo=webmail.mega-dev.net

Please can you help to resolve the issu and you will see below the email result

Code:
Delivered-To: [email protected]
Received: by 2002:ab0:c6:0:0:0:0:0 with SMTP id 64csp959070uaj;
        Tue, 5 Nov 2019 07:44:03 -0800 (PST)
X-Google-Smtp-Source: APXvYqzjU/4XFwhMOEszFTukIWccf9GHUsTWRVjvzXNO4eoWZGR2CBXxfLM+FqUGxOzRJ5NNxZcH
X-Received: by 2002:a7b:ca51:: with SMTP id m17mr4487011wml.110.1572968643457;
        Tue, 05 Nov 2019 07:44:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1572968643; cv=none;
        d=google.com; s=arc-20160816;
        b=NKcecQiq/RIwOMCKWhLQOJ+rq2ohGZght1m8kqMttDjUlg/QKI6ugbSV+Rc3NbqarO
         a2wCG/azREk3HYx9lJGQEqI97LXuvlFVRmiXuQG2HupOPZ4IKAYD9/FbzMwYqBHe+JLp
         Umg4+VvpW4M/INcb4XtKHntSbxMXbeh+KfYhWglPf2Bc8ilJExvWoVLEG3PYy+7BTdEJ
         AZIYgqotJtv1niuj1SYhdN2I/l7G/tJTLcOlF9QfW7/hxRdm2aLS8XppWUTBNX7Q1EQQ
         m3qL5mc3400qolMjzMhOyZxiAw3HM6ACzvT6PQg23FRFGANgpM9mGnLG4tKfkKo7uuaD
         DNdA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=user-agent:message-id:organization:subject:to:from:date
         :content-transfer-encoding:mime-version:dkim-signature;
        bh=v/84tV48ZRWRi1/6pr5a+2ZyAjXuQj2ONPRImFYPjJg=;
        b=VAgqgsq33RCpGakEE+/S8nOSkP+990iS4Xq1BTle1OkQw1hfVnyl5r3SWC7v0vziyW
         CRbyTaQNchrnjkQhrvAS9mdaXKJCHuuE/wMZfd0tHlkHuriZsWcWH1SYx2meGWoJndoB
         YXuiMETwbmPLTxGPdeL2vVfTDxmAvFasBoGxLYVNB52lawkT4vLQ+NGJQ8ULArpJs32e
         jka5Sq0R3kNDox8rAoEDB4PKlPwLOLTuulkJe1ko5dEih1Q30NPNT2yKPw5FkiA/bMUO
         /TF3kRj7nMKYBI+G0Pr+cNvbdDGL8Qax5wFPh6hlVNbNjdA+gK5scVzchWq2m8B/sebX
         LBGg==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass [email protected] header.s=default header.b=uzaEQgIc;
       spf=pass (google.com: domain of [email protected] designates 207.180.207.212 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mega-dev.net
Return-Path: <[email protected]>
Received: from mail.mega-dev.net (mail.mega-dev.net. [207.180.207.212])
        by mx.google.com with ESMTPS id a202si18885309wmd.126.2019.11.05.07.44.03
        for <[email protected]>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 05 Nov 2019 07:44:03 -0800 (PST)
Received-SPF: pass (google.com: domain of [email protected] designates 207.180.207.212 as permitted sender) client-ip=207.180.207.212;
Authentication-Results: mx.google.com;
       dkim=pass [email protected] header.s=default header.b=uzaEQgIc;
       spf=pass (google.com: domain of [email protected] designates 207.180.207.212 as permitted sender) [email protected];
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=mega-dev.net
Received: from webmail.mega-dev.net (mail.mega-dev.net [127.0.0.1]) by mail.mega-dev.net (Postfix) with ESMTPSA id 72D498C026E for <[email protected]>; Tue,
  5 Nov 2019 16:44:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mega-dev.net; s=default; t=1572968642; bh=v/84tV48ZRWRi1/6pr5a+2ZyAjXuQj2ONPRImFYPjJg=; h=From:To:Subject; b=uzaEQgIcULP9wv2PnwT/Jr++w8oj8PgeK9z/dUMOQqIN5p8GDxJFbCCy5VTmcTMix
     BmpoZ3pSBQzpNueJJMnU+SoE27eihVCrdw70vhcDV8b4uSNJzvjopr9U5Bve84Aqeh
     tcouMcDMsvD/hIzfUgZ3ANEBXb43QM9fXkR1/BfY=
Authentication-Results: mail.mega-dev.net;
        spf=pass (sender IP is 127.0.0.1) [email protected] smtp.helo=webmail.mega-dev.net
Received-SPF: pass (mail.mega-dev.net: connection is authenticated)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Tue, 05 Nov 2019 16:44:02 +0100
From: Mega DEV <[email protected]>
To: [email protected]
Subject: thank you for the service
Organization: MegaDEV LTD,
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.3.10
X-PPP-Message-ID: <[email protected]>
X-PPP-Vhost: mega-dev.net
 
So Gmail is treating your emails as spam?

The 127.0.0.1 you're seeing in connection with webmail is OK, don't worry about it. Also, your SPF, DKIM and rDNS seem to be in order. I have also checked if the IP 207.180.207.212 is included in spam lists and it seems to be clean.

That's about as much as you can do.

There are other factors that you might have less influence about, such as the history of the IP or your domain name, as Google sees it.

Unfortunately, Google will not tell you the reasons for considering mail to be spam or much else. Have you already used Google Postmaster? That's about as far as you'll get...
 
Hi Pleskers , Please I need your help
Your email seems perfectly fine. See my screenshots. Open email in gmail (i mean email which is ending in SPAM folder). Click on "Show Original" (see my screenshot 1). Then tell us does your screenshot look like this (screenshot 2)?

If it is - then everything is fine with your email. There are many reasons why your email message end in your specific gmail account spam folder (even though technically it's normal email). Have you tried to send it to different gmail accounts?

Could you also try (it's free) Email Deliverability Tool - Check Your Deliverability Report - MxToolBox and tell us result?
 

Attachments

  • 1.jpg
    1.jpg
    89.8 KB · Views: 36
  • 2.jpg
    2.jpg
    125.4 KB · Views: 34
hello @Ales , yes before i re-install my server i used it , it generate for me a TXT record i put it and verified my domain
but now i did not use it , i dont know if i should put the dns record again or no to validate domain !!??

hello @seqoi yes i the gmail header , everything is pass , also i tested the deliveribilty with mxtoolsbox and you will see the result in the screenshot
I dont know why the 127.0.0.1 is for webmail is created in the header , ?? and not the ip adress of the server !!

can you help me and tell me how can i change the webmail ip adress on the header from 127.0.0.1 to the ip adress of the server !!
 

Attachments

  • 2019-11-06 10.28.12 mxtoolbox.com c98e5336022b.jpg
    2019-11-06 10.28.12 mxtoolbox.com c98e5336022b.jpg
    803.1 KB · Views: 30
hello @seqoi yes i the gmail header , everything is pass , also i tested the deliveribilty with mxtoolsbox and you will see the result in the screenshot
I dont know why the 127.0.0.1 is for webmail is created in the header , ?? and not the ip adress of the server !!

can you help me and tell me how can i change the webmail ip adress on the header from 127.0.0.1 to the ip adress of the server !!

Kais you are mistaken. Your email IP is correct and it's from your server 207.180.207.212 (on top of that you see [email protected] designates 207.180.207.212 as permitted sender)

That 127.0.0.1 is not your server IP address (but i can understand that it confuses you). It's virtual IP from service running to send emails(webmail). To give you another perspective if i run same result on mxtoolbox from my Plesk server i am also getting something different then my real server IP :) - that is normal and this is not the reason why your email ends up in Gmail spam folder

Anyway i will try to provide you few plausible reasons why google think you are Spam for this specific issue:

- it can be that IP address of your server sometimes in history was in blacklist (it's not now but perhaps sometimes at some point of time it was)
- it can be that someone, a person or few people when reading their emails in Gmail marked emails coming from your domain as a SPAM - which is resulting Gmail thinking yemails from your domain are Spam.

What you can do is this:

Try to send email to other people, some of your colleagues or friends who own Gmail account. Send them same email to their Gmail address and ask them did it arrived correctly to inbox or to their Spam folders? If your email arrived correctly in their inbox then it's only your account (kaisjrad1990-at-gmail.com) acting strangely. You can then simply "teach" your gmail spam filter by selecting messages which are in spam and mark them as "not spam".

Also you can follow Google Postmaster, add records etc. As Alex suggested.
 
Last edited:
ok thank you very much for your reply and advice , i will try this

thanks again
 
Back
Top