Resolved Postfix send mail enup in spam

[NicolaiVdS]

Hello,

I have successfully added SPF, DKIM and Domainkeys + DMARC to my domain and for some reason the mails i send to Gmail, Hotmail etc end up into te spam folder. Are there any other actions i can take to make sure that the mails i send dont go into the spam folder ?

---Things i have checked---
result from check-auth@verifier.port25.com

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         pass
DKIM check:         pass
SpamAssassin check: ham

Ip Reputation is good and i'm not in any blacklist (test done on mxtoolbox)

 

[UFHH01]

Hi NicolaiVdS,

pls. provide the eMail - HEADER from the corresponding eMails, which are marked as spam at GMAIL/Hotmail/... - we can not guess such things.


Actually, you seem still to experiment with your settings, as the actual SPF - entry "v=spf1 mx a ptr ip4:78.31.64.48/32 ?all" differs from the previous one "v=spf1 +a +mx +alesk.nvds.be -all".
The recommended SPF - entry is for example: "v=spf1 +mx +a alesk.nvds.be ip4:78.31.64.48 ?all" - nothing more, nothing less.

According to => http://mxtoolbox.com/domain/nvds.be/ , you are previously/currently blacklisted at "ivmSIP24" with "nvds.be" and "mail.nvds.be" and the IP "78.31.64.48". There is a REASON, why you got on this list, so pls. consider to resolve that issue.
Additional informations from MXTOOLBOX:

More Information About Ivmsip24
Listing in the ivmSIP/24 blacklists indicates that your IP Address has been identified as a spam-sending server, or is in a range of IP Addresses of a host-provider that includes spending-sending servers; hence the "/24" block reference. Whether or not you operate an email-server on this IP Address, it has either sent spam or has been previously identified as such.

Ivmsip24 Reports Subnets
Subnet-based Blacklists are used to reject email from entire ranges of IP Addresses, i.e. providers that are hosting companies sending spam, as well as single IP Addresses that may fall in that range of IP Address.


More information about ivmSIP24 can be found at their website: http://dnsbl.invaluement.com/ivmsip24/

Reason for listing - Blocked by ivmSIP/24 - see http://dnsbl.invaluement.com/lookup/?item=78.31.64.48

 

[NicolaiVdS]

Hi NicolaiVdS,

pls. provide the eMail - HEADER from the corresponding eMails, which are marked as spam at GMAIL/Hotmail/... - we can not guess such things.


Actually, you seem still to experiment with your settings, as the actual SPF - entry "v=spf1 mx a ptr ip4:78.31.64.48/32 ?all" differs from the previous one "v=spf1 +a +mx +alesk.nvds.be -all".
The recommended SPF - entry is for example: "v=spf1 +mx +a alesk.nvds.be ip4:78.31.64.48 ?all" - nothing more, nothing less.

According to => http://mxtoolbox.com/domain/nvds.be/ , you are previously/currently blacklisted at "ivmSIP24" with "nvds.be" and "mail.nvds.be" and the IP "78.31.64.48". There is a REASON, why you got on this list, so pls. consider to resolve that issue.
Additional informations from MXTOOLBOX:

Here you go for the eMail header

Delivered-To: vds.nicolai@gmail.com
Received: by 10.114.174.104 with SMTP id br8csp819593ldc;
        Sat, 26 Nov 2016 06:39:14 -0800 (PST)
X-Received: by 10.194.21.201 with SMTP id x9mr11291896wje.153.1480171154739;
        Sat, 26 Nov 2016 06:39:14 -0800 (PST)
Return-Path: <nicolai@nvds.be>
Received: from plesk.nvds.be (plesk.nvds.be. [78.31.64.48])
        by mx.google.com with ESMTPS id h5si18788620wmi.18.2016.11.26.06.39.14
        for <vds.nicolai@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sat, 26 Nov 2016 06:39:14 -0800 (PST)
Received-SPF: pass (google.com: domain of nicolai@nvds.be designates 78.31.64.48 as permitted sender) client-ip=78.31.64.48;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@nvds.be;
       dkim=pass header.i=@nvds.be;
       spf=pass (google.com: domain of nicolai@nvds.be designates 78.31.64.48 as permitted sender) smtp.mailfrom=nicolai@nvds.be;
       dmarc=pass (p=NONE dis=NONE) header.from=nvds.be
Received: from Nicolais-MacBook-Pro.local (unknown [IPv6:2a02:a03f:12dc:2a00:40aa:8c36:90a0:9f4]) by plesk.nvds.be (Postfix) with ESMTPSA id AB76392213B for <vds.nicolai@gmail.com>; Sat, 26 Nov 2016 15:39:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nvds.be; s=mail; t=1480171145; bh=SfYBDZiRVB6mLSy+4D8LC4HTHjiR88En74AkEgc4sGg=; h=To:From:Subject:Date:From; b=Thn6nKmsp//k/Y3PIG00TpDtfvNToEknrYxUo1B+Dc2k8NC0mqLA90KUyki4plvQ7
     ZJGVzojil6xKRAY2nYJIebYkCZKX2EfyzxdjNPsddavuUy6NVZvYVSb0SFrK9ck8Q/
     IBDLJSQHRVoKnhyG4ZGuAw4vslfOixqVzsUcO7Tg=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvds.be; s=default; t=1480171145; bh=SfYBDZiRVB6mLSy+4D8LC4HTHjiR88En74AkEgc4sGg=; l=7; h=To:From:Subject; b=HLOWOkAvN4rt8ryaP8aQz3Y55WLTz0nf+2m62PR1j4XmH4vKWTX1MOQqd66hyXRMQ
     s8pNpZ6sxWkVRvOBYBvdFdGcjsGxV2FI87Dp4WERuQJq12MQj7VuSctmixBdREVAIQ
     l0GFbV3mqyyvYxMtGIvt5hojtmzko0qx5SW0Wz1c=
To: vds.nicolai@gmail.com
From: Nicolai Van der Storm <nicolai@nvds.be>
Subject: hbeh
Message-ID: <becf0ed7-7595-930b-3d17-8e39fda7d3ce@nvds.be>
Date: Sat, 26 Nov 2016 15:39:13 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

ljhbl

also i have made a request to remove the ip from the blacklist

 

[UFHH01]

Received: from Nicolais-MacBook-Pro.local (unknown [IPv6:2a02:a03f:12dc:2a00:40aa:8c36:90a0:9f4]) by plesk.nvds.be (Postfix) with ESMTPSA id AB76392213B for <vds.nicolai@gmail.com>; Sat, 26 Nov 2016 15:39:05 +0100 (CET)

Guideline from Google => https://support.google.com/mail/answer/81126 :

...
Additional guidelines for IPv6

• The sending IP must have a PTR record (i.e., a reverse DNS of the sending IP) and it should match the IP obtained via the forward DNS resolution of the hostname specified in the PTR record. Otherwise, mail will be marked as spam or possibly rejected.

...

Reverse DNS of IPv6 - address => "2a02:a03f:12dc:2a00:40aa:8c36:90a0:9f4" => No name server returned any records for this request.

IP address: 2a02:a03f:12dc:2a00:40aa:8c36:90a0:9f4
Reverse DNS: No Reverse DNS found
Reverse DNS Authenticity: Unknown
Country: Belgium

 

[NicolaiVdS]

Guideline from Google => https://support.google.com/mail/answer/81126 :


Reverse DNS of IPv6 - address => "2a02:a03f:12dc:2a00:40aa:8c36:90a0:9f4" => No name server returned any records for this request.

thats my own ip and not of the server it the one my isp delivers to me :s so what can i do to reslove this ?? only accept ipv4 connections ?

 

[UFHH01]

Hi NicolaiVdS,

thats my own ip

yes, that's your own IP and it doesn't have a correct PTR. It's the SENDING IP from your MAIL - CLIENT, which causes the "marked-as-spam" - issues here, when your own IPv6 - address can't be resolved - in your specific ( unique ) case, it is recommended to only accept IPv4 - connections to avoid such issues. If you would like a better answer ( which would not exclude IPv6 - usage ), pls. contact your ISP and aks them, how you are able to resolve an IPv6 to a FQDN.

 

[NicolaiVdS]

Hi NicolaiVdS,


yes, that's your own IP and it doesn't have a correct PTR. It's the SENDING IP from your MAIL - CLIENT, which causes the "marked-as-spam" - issues here, when your own IPv6 - address can't be resolved - in your specific ( unique ) case, it is recommended to only accept IPv4 - connections to avoid such issues. If you would like a better answer ( which would not exclude IPv6 - usage ), pls. contact your ISP and aks them, how you are able to resolve an IPv6 to a FQDN.

Thanks for the great support i will do 2 things only allow ipv4 connections for now and contact my and other isp's that deliver ipv6 to there client to make sure to add a FQFN to there ipv6 rdns

 

[NicolaiVdS]

Thanks for the great support i will do 2 things only allow ipv4 connections for now and contact my and other isp's that deliver ipv6 to there client to make sure to add a FQFN to there ipv6 rdns

in other news my isp's ipv4 dont have a decent rdns -_-

Received: from Nicolais-MacBook-Pro.local (unknown [91.181.196.182]) by plesk.nvds.be (Postfix) with ESMTPSA id CEB7C9216EE for <deliemoilekes@gmail.com>; Sun, 27 Nov 2016

Reverse DNS to 91.181.196.182

IP address: 91.181.196.182
Reverse DNS: 182.196-181-91.adsl-dyn.isp.belgacom.be
Reverse DNS Authenticity: Could be forged: Hostname '182.196-181-91.adsl-dyn.isp.belgacom.be' does not exist
Country: Belgium

 

[UFHH01]

in other news my isp's ipv4 dont have a decent rdns -_-

correct.

 

[NicolaiVdS]

correct.

so i did some testing the ip is also from the blacklist but the mails still end up in the spam folder

gmail headers

Delivered-To: deliemoilekes@gmail.com
Received: by 10.83.42.72 with SMTP id q69csp1277067yxq;
        Sun, 27 Nov 2016 12:21:30 -0800 (PST)
X-Received: by 10.28.164.196 with SMTP id n187mr15663734wme.44.1480278090065;
        Sun, 27 Nov 2016 12:21:30 -0800 (PST)
Return-Path: <nicolai@nvds.be>
Received: from plesk.nvds.be (plesk.nvds.be. [78.31.64.48])
        by mx.google.com with ESMTPS id jp8si51789477wjc.10.2016.11.27.12.21.29
        for <deliemoilekes@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sun, 27 Nov 2016 12:21:29 -0800 (PST)
Received-SPF: pass (google.com: domain of nicolai@nvds.be designates 78.31.64.48 as permitted sender) client-ip=78.31.64.48;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@nvds.be;
       dkim=pass header.i=@nvds.be;
       dkim=pass header.i=@nvds.be;
       dkim=pass header.i=@nvds.be;
       spf=pass (google.com: domain of nicolai@nvds.be designates 78.31.64.48 as permitted sender) smtp.mailfrom=nicolai@nvds.be;
       dmarc=pass (p=NONE dis=NONE) header.from=nvds.be
Received: by plesk.nvds.be (Postfix, from userid 10003) id C05E59215FA; Sun, 27 Nov 2016 21:21:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nvds.be; s=mail; t=1480278077; bh=a2uE0EnMRwXpyroyF4fWfPCeTPTEOgIx3Sc0OHhSKfw=; h=Date:From:Subject:To:From; b=JvvhB+5rcycNQpmKYFgUfPY8wdJy36eiknvtnf+1BTZirnxBEz1iayQcpw9B3nmWs
     yE5rRFMOfuGFrDHBH+sA1rwJ1OOE+FFXXUKRo4MI27A61HNd+TkCsyS8dQCswu+RnL
     SOCZ5U6Tp/jvlazyPDo13V1eOEx2eg1byBigYh7k=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvds.be; s=default; t=1480278077; bh=a2uE0EnMRwXpyroyF4fWfPCeTPTEOgIx3Sc0OHhSKfw=; l=731; h=Received:From:Subject:To; b=aKyGv8cH4DGPsgPVOioVUU1o1j4Z7H9bpy3hMWyCNUGSvdUX2B0PvaKmtsz75OnVf
     EW1A6Ekj/4+VPZEKpj+7uoVbZFOhU1IlN1rmrJZwlZ5Bm5b7czd/7iEtuV0K4qjFFi
     POSBtmvjuuC36dTyHKnsWE87b8GzPueVH5+he9Sk=
Received-SPF: pass (plesk.nvds.be: localhost is always allowed.) client-ip=127.0.0.1; envelope-from=nicolai@nvds.be; helo=localhost;
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on plesk.nvds.be
X-Spam-Level:
X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED,HTML_MESSAGE, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.0
Received: from mail.nvds.be (localhost.localdomain [127.0.0.1]) by plesk.nvds.be (Postfix) with ESMTPSA id 11871921326 for <deliemoilekes@gmail.com>; Sun, 27 Nov 2016 21:21:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nvds.be; s=mail; t=1480278077; bh=a2uE0EnMRwXpyroyF4fWfPCeTPTEOgIx3Sc0OHhSKfw=; h=Date:From:Subject:To:From; b=JvvhB+5rcycNQpmKYFgUfPY8wdJy36eiknvtnf+1BTZirnxBEz1iayQcpw9B3nmWs
     yE5rRFMOfuGFrDHBH+sA1rwJ1OOE+FFXXUKRo4MI27A61HNd+TkCsyS8dQCswu+RnL
     SOCZ5U6Tp/jvlazyPDo13V1eOEx2eg1byBigYh7k=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvds.be; s=default; t=1480278077; bh=a2uE0EnMRwXpyroyF4fWfPCeTPTEOgIx3Sc0OHhSKfw=; l=731; h=From:Subject:To; b=ZV0wZPsZejQq9DDqqSy4gyF1faq3oW+atTyxim0luQRDvIuyOJvmKcU5Yjunm9G9f
     Lx8Gb6A1Jn1LmGBXb2RginrdpgvImukoSkTH7H7DxAI+y6kGOooz1MEFl0AnOA5ug6
     mD+E1gOgKGbFIRcJ2rO9JSQQfePuFdoORWmdgMtM=
Mime-Version: 1.0
Date: Sun, 27 Nov 2016 20:21:17 +0000
Content-Type: multipart/alternative; boundary="----=_Part_895_488432851.1480278077"
Message-ID: <a9f46a42859cd50f68487850025491c3@mail.nvds.be>
X-Mailer: AfterLogic webmail client
From: nicolai@nvds.be
Subject: Nicolai VdS
To: deliemoilekes@gmail.com
X-Priority: 3 (Normal)

------=_Part_895_488432851.1480278077
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Beste,

Bij deze laat ik je weten dat Nicolai VdS niet langer een lid is

------=_Part_895_488432851.1480278077
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><meta http-equiv=3D"Content-Type" content=3D"tex=
t/html; charset=3Dutf-8" /></head><body><div data-crea=3D"font-wrapper" sty=
le=3D"font-family: Tahoma; font-size: 16px; direction: ltr">Beste,<br><br>B=
ij deze laat ik je weten dat Nicolai VdS niet langer een lid is <br><br><di=
v></div><br></div></body></html>

------=_Part_895_488432851.1480278077--

hotmail: http://pastebin.com/QEg6yw2y

Note mails are send from roundcube webmail

 

[UFHH01]

Hi NicolaiVdS,

are you aware, that you have the chance with GMail for example, to see WHY the message has been declared as spam? => https://gmail.googleblog.com/2012/03/learn-why-message-ended-up-in-your-spam.html

At the moment, with your current settings, you should be fine and mails from your domain "nvds.be" should not be declared as spam. Other possible solutions ( contacting GMail - suport, whitelisting domain or eMail - adresses in GMAIL, ... ) are absolutely not plesk-related.
Pls. choose for example to contact GMail here: => https://support.google.com/mail/contact/msgdelivery

 

[hoangnguyen]

Hi UFHH01,
I also have problem when i send mail to gmail, hotmail allway into spam box. I have successfully config SPF, DKIM, PTR Record.
Result from check-auth@verifier.port25.com:

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         pass
DKIM check:         pass
SpamAssassin check: ham

Mail header when send to Gmail

Delivered-To: lehoangnguyen17111992@gmail.com
Received: by 10.194.23.99 with SMTP id l3csp2119621wjf;
        Mon, 28 Nov 2016 19:35:58 -0800 (PST)
X-Received: by 10.84.146.140 with SMTP id g12mr57601768pla.157.1480390557951;
        Mon, 28 Nov 2016 19:35:57 -0800 (PST)
Return-Path: <lehoangnguyen@cosmomedical.com.vn>
Received: from cosmomedical.com.vn (cosmomedical.com.vn. [49.156.52.62])
        by mx.google.com with ESMTPS id d10si29276831plj.113.2016.11.28.19.35.57
        for <lehoangnguyen17111992@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 28 Nov 2016 19:35:57 -0800 (PST)
Received-SPF: pass (google.com: domain of lehoangnguyen@cosmomedical.com.vn designates 49.156.52.62 as permitted sender) client-ip=49.156.52.62;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@cosmomedical.com.vn;
       dkim=pass header.i=@cosmomedical.com.vn;
       spf=pass (google.com: domain of lehoangnguyen@cosmomedical.com.vn designates 49.156.52.62 as permitted sender) smtp.mailfrom=lehoangnguyen@cosmomedical.com.vn
Received: from cosmomedical.com.vn (localhost [127.0.0.1]) by cosmomedical.com.vn (Postfix) with ESMTP id CE9681814C5 for <lehoangnguyen17111992@gmail.com>; Tue, 29 Nov 2016 10:35:54 +0700 (ICT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cosmomedical.com.vn; s=default; t=1480390554; bh=eBZ0/dfp7D1p0kPy7Te2/WDH9GVgvMBCWkYB3yv8uUI=; h=Date:From:Subject:To; b=uSSO+pO9utu1OliF0uy17xwgarYG1gScQc+5DF/ypKgOp2FoWthFmkVcQmUQse977
     ISrJwQWd3XRgWrgwGQ3N8xsAp38j1QWsCOF98klHvifweuVIdogsybgTjZ+TAOrtG+
     ga/PkQR3OrCR3piNYulKV2atcOSNupV1KbQZogSU=
Received: from cosmomedical.com.vn (cosmomedical.com.vn [192.168.1.240]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: lehoangnguyen) by cosmomedical.com.vn (Postfix) with ESMTPSA id A30111814C3 for <lehoangnguyen17111992@gmail.com>; Tue, 29 Nov 2016 10:35:54 +0700 (ICT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cosmomedical.com.vn; s=default; t=1480390554; bh=eBZ0/dfp7D1p0kPy7Te2/WDH9GVgvMBCWkYB3yv8uUI=; h=Date:From:Subject:To; b=uSSO+pO9utu1OliF0uy17xwgarYG1gScQc+5DF/ypKgOp2FoWthFmkVcQmUQse977
     ISrJwQWd3XRgWrgwGQ3N8xsAp38j1QWsCOF98klHvifweuVIdogsybgTjZ+TAOrtG+
     ga/PkQR3OrCR3piNYulKV2atcOSNupV1KbQZogSU=
Mime-Version: 1.0
Date: Tue, 29 Nov 2016 03:35:54 +0000
Content-Type: multipart/alternative; boundary="--=_RainLoop_540_676415301.1480390554"
Message-ID: <46ee6fcd81c13e48bf51b874d59ff715@cosmomedical.com.vn>
X-Mailer: RainLoop/1.10.4.183
From: Le Hoang Nguyen <lehoangnguyen@cosmomedical.com.vn>
Subject: test
To: lehoangnguyen17111992@gmail.com
X-Virus-Scanned: ClamAV using ClamSMTP

----=_RainLoop_540_676415301.1480390554
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

test

----=_RainLoop_540_676415301.1480390554
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><meta http-equiv=3D"Content-Type" content=3D"tex=
t/html; charset=3Dutf-8" /></head><body><html><body><div><div data-html-edi=
tor-font-wrapper=3D"true" style=3D"font-family: arial, sans-serif; font-siz=
e: 13px;"><signature>test</signature></div></div></body></html></body></htm=
l>

----=_RainLoop_540_676415301.1480390554--

Show log postfix, i see a problem:

Nov 29 10:41:17 cosmomedical postfix/smtp[24051]: connect to gmail-smtp-in.l.google.com[2404:6800:4003:c02::1a]:25: Network is unreachable
Nov 29 10:41:18 cosmomedical postfix/smtp[24051]: setting up TLS connection to gmail-smtp-in.l.google.com[74.125.200.26]:25
Nov 29 10:41:18 cosmomedical postfix/smtp[24051]: Trusted TLS connection established to gmail-smtp-in.l.google.com[74.125.200.26]:25: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)

so, please give me a reason or solution.

 

[UFHH01]

Hi hoangnguyen,

connect to gmail-smtp-in.l.google.com[2404:6800:4003:c02::1a]:25: Network is unreachable

As you can see, the request over IPv6 at port 25 was "unreachable". This happens, when ISPs are blocking the port to avoid spam. Pls. contact your ISP if you experience such issues.
If you don't have any IPv6 on your server, pls. consider to remove IPv6 - support on your server, to avoid such error - messages.

Nov 29 10:41:18 cosmomedical postfix/smtp[24051]: setting up TLS connection to gmail-smtp-in.l.google.com[74.125.200.26]:25 Nov 29 10:41:18 cosmomedical postfix/smtp[24051]: Trusted TLS connection established to gmail-smtp-in.l.google.com[74.125.200.26]:25: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)

On the other hand, the request over IPv4 on port 25 was successfull.


Apart from the above issues ( which are not relevant for a "spam - declaration" for GMail/Hotmail ), I noticed some slow nameservers

Searching for ns3.vdc3.vn. A record at ns2.vdc3.vn. [203.162.31.100]
Query timed out (interrupted after 2,002 milliseconds)

Searching for ns3.vdc3.vn. A record at ns3.vdc3.vn. [203.162.31.113]
Query timed out (interrupted after 2,002 milliseconds)

Searching for cosmomedical.com.vn. A record at ns3.vdc3.vn. [203.162.31.113]
Query timed out (interrupted after 2,002 milliseconds)

... which is as well not relevant for "spam - declarations", but this can result in request - time-outs, while your server requests DNS entries, or when corresponding mail - servers request DNS - entries.
Pls. be aware, that static DSL/Cable - IPs are not really the same as "100 Mbit/s" + "1 Gbit/s" connections, which you get from for example server - hosting - providers., when it comes to "performance", "speed" and "fast path" . You will always experience such issues with Cable/DSL - IPs.


In addition, you could add as well "DMARC" - entries for your domains. A valid "DMARC" - record for "cosmomedical.com.vn" is missing. You could avoid "spam - declarations", when you setup "DMARC" - records.


Last, it has to be mentioned, that IP-Blocks/IP-Ranges for Cable/DSL - IPs from asia ( China/Vietnam/Indonesia/Russia... ) have a very bad reputation ( spam-bots/scripts/hackers/... ) and this results in a lot of bans and spam - declarations for these IPs and their corresponding domains. Pls. consider as well to read the answer => #11 .

 

[hoangnguyen]

Hi hoangnguyen,


As you can see, the request over IPv6 at port 25 was "unreachable". This happens, when ISPs are blocking the port to avoid spam. Pls. contact your ISP if you experience such issues.
If you don't have any IPv6 on your server, pls. consider to remove IPv6 - support on your server, to avoid such error - messages.


On the other hand, the request over IPv4 on port 25 was successfull.


Apart from the above issues ( which are not relevant for a "spam - declaration" for GMail/Hotmail ), I noticed some slow nameservers

Searching for ns3.vdc3.vn. A record at ns2.vdc3.vn. [203.162.31.100]
Query timed out (interrupted after 2,002 milliseconds)

Searching for ns3.vdc3.vn. A record at ns3.vdc3.vn. [203.162.31.113]
Query timed out (interrupted after 2,002 milliseconds)

Searching for cosmomedical.com.vn. A record at ns3.vdc3.vn. [203.162.31.113]
Query timed out (interrupted after 2,002 milliseconds)

... which is as well not relevant for "spam - declarations", but this can result in request - time-outs, while your server requests DNS entries, or when corresponding mail - servers request DNS - entries.
Pls. be aware, that static DSL/Cable - IPs are not really the same as "100 Mbit/s" + "1 Gbit/s" connections, which you get from for example server - hosting - providers., when it comes to "performance", "speed" and "fast path" . You will always experience such issues with Cable/DSL - IPs.


In addition, you could add as well "DMARC" - entries for your domains. A valid "DMARC" - record for "cosmomedical.com.vn" is missing. You could avoid "spam - declarations", when you setup "DMARC" - records.


Last, it has to be mentioned, that IP-Blocks/IP-Ranges for Cable/DSL - IPs from asia ( China/Vietnam/Indonesia/Russia... ) have a very bad reputation ( spam-bots/scripts/hackers/... ) and this results in a lot of bans and spam - declarations for these IPs and their corresponding domains. Pls. consider as well to read the answer => #11 .

Hi UFHH01,
Thank you for reply and help.
I use Parallels Plesk Panel 9.5, so I try to add DMARC but can't. Seem Plesk Panel 9.5 cannot add DMARC? or if can, please help me how to config it.

 

[Oscar Segura]

First of all, and to clarify why answering an old topic: there is always the issue of not having decided under which domain you will add your sever when doing a Plesk installation. So it may help someone reaching here if used "localhost.localdomain" as searching criterion.

Received: from mail.nvds.be (localhost.localdomain [127.0.0.1]) by plesk.nvds.be (Postfix) with ESMTPSA id 11871921326 for <deliemoilekes@gmail.com>; Sun, 27 Nov 2016 21:21:17 +0100 (CET)

Your hostname was the issue: localhost.localdomain

1. You can test your email server at http://mxtoolbox.com/diagnostic.aspx to detect which all the issues are.

2. To change the hostname:

root@localhost# plesk bin server_pref --update -hostname servername.your-domain.tld
root# reboot
.....
root@servername#

NOTE: you should never give your server a name containing only the naked domain name (i.e. your-domain.tld), not least of one of the reasons is that it causes mail delivery to go haywire (reasons, source)​

3. Then you will need to create the DNS PTR Record (the reverse DNS). Your domain provider should allow you to change the Reverse DNS. If you manage your own DNS server, then you will need to create the PTR record yourself manually (here a clear manual to understand how to do it).

4. You will need to create an DNS A Record (AAAA for IPv6) from your server domain (hostname) to the @IP, so the lookup the other way is working (reference)


The above all the main points, but not the only ones. You might add some other TXT DNS records for spf1 to enable your main domain (i.e. your-domain.tld) acting in behalf of other domains hosted in the same sever as email server. This part can by tricky and I will not provide further details here. But there are some good pages to learn how to create those DNS entries to "link" your respective domains and your main domain (just say that it entails to create at least one entry for each DNS server of each domain; not just the spf1 policy for the main domain => the other domains should reference/delegate to the spf1 policy of the main domain).