Well, I did search for results about this before posting here, also contacted Google via the contact form and provided every detail possible. I have checked that I have MX, PTR, SPF, DKIM, DMARC setup correctly:
https://intodns.com/fsgaz.ro
https://mxtoolbox.com/domain/fsgaz.ro/
Problem is that I cannot send to Gmail, to be more precise, Gmail rejects my email with: "Remote server replied: 550-5.7.1 [81.180.119.90 19] Our system has detected that this message is 550-5.7.1 likely suspicious due to the very low reputation of the sending 550-5.7.1 domain."
Code: Select all
Return-Path:
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Return-Path: <>
Message-ID: <4C42C2BB-5AEA-4E7D-AE6D-35A0B8B6ACB3@mail.fsgaz.ro>
Date: Fri, 26 Jan 2018 18:03:46 +0200
From: mailer-daemon@mail.fsgaz.ro
To: admin@fsgaz.ro
Subject: Message undeliverable: test catre gmail
Content-Transfer-Encoding: quoted-printable
X-hMailServer-LoopCount: 1
Your message did not reach some or all of the intended recipients.\r\n\r\n Sent: Fri, 26 Jan 2018 18:03:46 +0200\r\n Subject: test catre gmail\r\n\r\nThe following recipient(s) could not be reached:\r\n\r\nadrianmihai83@gmail.com
Error Type: SMTP
Remote server (74.125.133.27) issued an error.
hMailServer sent: .
Remote server replied: 550-5.7.1 [81.180.119.90 19] Our system has detected that this message is
550-5.7.1 likely suspicious due to the very low reputation of the sending
550-5.7.1 domain. To best protect our users from spam, the message has been
550-5.7.1 blocked. Please visit
550 5.7.1 https://support.google.com/mail/answer/188131 for more information. g131si2776578wma.139 - gsmtp
\r\n\r\nhMailServer\r\n
Code: Select all
This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com. The service allows email senders to perform
a simple check of various sender authentication mechanisms. It is provided
free of charge, in the hope that it is useful to the email community. While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.
Thank you for using the verifier,
The Port25 Solutions, Inc. team
==========================================================
Summary of Results
==========================================================
SPF check: pass
"iprev" check: pass
DKIM check: pass
SpamAssassin check: ham
==========================================================
Details:
==========================================================
HELO hostname: mail.fsgaz.ro
Source IP: 81.180.119.90
mail-from: admin@fsgaz.ro
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mailfrom=admin@fsgaz.ro
DNS record(s):
fsgaz.ro. 3428 IN TXT "v=spf1 mx a ip4:81.180.119.90 ~all"
fsgaz.ro. 3428 IN MX 10 mail.fsgaz.ro.
mail.fsgaz.ro. 3428 IN A 81.180.119.90
----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result: pass (matches mail.fsgaz.ro)
ID(s) verified: policy.iprev=81.180.119.90
DNS record(s):
90.119.180.81.in-addr.arpa. 86228 IN PTR mail.fsgaz.ro.
mail.fsgaz.ro. 3428 IN A 81.180.119.90
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass (matches From: admin@fsgaz.ro)
ID(s) verified: header.d=fsgaz.ro
Canonicalized Headers:
from:admin@fsgaz.ro'0D''0A'
subject:test'20'email'0D''0A'
date:Fri,'20'26'20'Jan'20'2018'20'17:05:42'20'+0200'0D''0A'
message-id:<2.669fcfb7bdb080d42a52@SERVER-FSGAZ1>'0D''0A'
to:check-auth@verifier.port25.com'0D''0A'
mime-version:1.0'0D''0A'
content-type:multipart/alternative;'20'boundary="----=_NextPart_000_BEB7_9BF727CF.A5C8F89D"'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha256;'20'd=fsgaz.ro;'20's=all;'20'c=relaxed/relaxed;'20'q=dns/txt;'20'h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type;'20'bh=iBivMu5brUTAGc57gvRNAkBuHpADxyVEBwhJyMYmTDA=;'20'b=
Canonicalized Body:
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D'0D''0A'
Content-Type:'20'text/plain;'0D''0A'
'20'charset="utf-8"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
test'0D''0A'
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D'0D''0A'
Content-Type:'20'text/html;'0D''0A'
'20'charset="utf-8"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
<html><body>test</body></html>'0D''0A'
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D--'0D''0A'
DNS record(s):
all._domainkey.fsgaz.ro. 3600 IN TXT "k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxAQDCtp78BkfBFQWkPDQUIvPoByuuR+p717EA1X8DIvWx22kBfkwgyAfP8cDcYXZ946htIFX/IHvTPset/XE2VSUX0TpMOBOSzMiksroWAB2DH1WmC04opiWG0KcKOgJFLAowWSzqnUcZvpmNYNv+6SjaY7iuYYxs63Ws/AViThganR40z8l27uoqu/onxBi0kZ7QKKNqxm557zyDU7cDLx434LlEi+ynYF752LpN2rSw/wrr5lO2T44RdbAQJMF7hy+gjP0WLQJlYKY1OQDotl+mYMx8uY3OocB2Lz+52TXXB9i8f3FNjXtkJaYG2YuD7RPug3rFufZr6z/o4x5FwIDAQAB"
Public key used for verification: all._domainkey.fsgaz.ro (2048 bits)
NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.4.1 (2015-04-28)
Result: ham (-0.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
0.0 T_SPF_TEMPERROR SPF: test of record failed (temperror)
0.0 T_SPF_HELO_TEMPERROR SPF: test of HELO record failed (temperror)
-0.0 BAYES_40 BODY: Bayes spam probability is 20 to 40%
[score: 0.3255]
0.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
==============================================================
Explanation of the possible results (based on RFCs 7601, 7208)
==============================================================
DKIM Results
============
none: The message was not signed.
pass: The message was signed, the signature or signatures were
acceptable to the ADMD, and the signature(s) passed verification
tests.
fail: The message was signed and the signature or signatures were
acceptable to the ADMD, but they failed the verification test(s).
policy: The message was signed, but some aspect of the signature or
signatures was not acceptable to the ADMD.
neutral: The message was signed, but the signature or signatures
contained syntax errors or were not otherwise able to be
processed. This result is also used for other failures not
covered elsewhere in this list.
temperror: The message could not be verified due to some error that
is likely transient in nature, such as a temporary inability to
retrieve a public key. A later attempt may produce a final
result.
permerror: The message could not be verified due to some error that
is unrecoverable, such as a required header field being absent. A
later attempt is unlikely to produce a final result.
SPF Results
===========
none: Either (a) no syntactically valid DNS domain name was extracted from
the SMTP session that could be used as the one to be authorized, or
(b) no SPF records were retrieved from the DNS.
neutral: The ADMD has explicitly stated that it is not asserting whether
the IP address is authorized.
pass: An explicit statement that the client is authorized to inject mail
with the given identity.
fail: An explicit statement that the client is not authorized to use the
domain in the given identity.
softfail: A weak statement by the publishing ADMD that the host is probably
not authorized. It has not published a stronger, more definitive policy
that results in a "fail".
temperror: The SPF verifier encountered a transient (generally DNS) error
while performing the check. A later retry may succeed without further
DNS operator action.
permerror: The domain's published records could not be correctly interpreted.
This signals an error condition that definitely requires DNS operator
intervention to be resolved.
"iprev" Results
===============
pass: The DNS evaluation succeeded, i.e., the "reverse" and
"forward" lookup results were returned and were in agreement.
fail: The DNS evaluation failed. In particular, the "reverse" and
"forward" lookups each produced results, but they were not in
agreement, or the "forward" query completed but produced no
result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an
RCODE of 0 (NOERROR) in a reply containing no answers, was
returned.
temperror: The DNS evaluation could not be completed due to some
error that is likely transient in nature, such as a temporary DNS
error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or
other error condition resulted. A later attempt may produce a
final result.
permerror: The DNS evaluation could not be completed because no PTR
data are published for the connecting IP address, e.g., a DNS
RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR)
in a reply containing no answers, was returned. This prevented
completion of the evaluation. A later attempt is unlikely to
produce a final result.
==========================================================
Original Email
==========================================================
Return-Path: <admin@fsgaz.ro>
Received: from mail.fsgaz.ro (81.180.119.90) by verifier.port25.com id hdd1sk2bkd08 for <check-auth@verifier.port25.com>; Fri, 26 Jan 2018 10:05:46 -0500 (envelope-from <admin@fsgaz.ro>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=admin@fsgaz.ro;
iprev=pass (matches mail.fsgaz.ro) policy.iprev=81.180.119.90;
dkim=pass (matches From: admin@fsgaz.ro) header.d=fsgaz.ro
dkim-signature: v=1; a=rsa-sha256; d=fsgaz.ro; s=all;
c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type;
bh=iBivMu5brUTAGc57gvRNAkBuHpADxyVEBwhJyMYmTDA=;
b=eZnOPePdBoqK/qL/8mYZofzvyoYdx5EgtVWq0jsRwn+7wHk3z2Duf+FT4QRHzoWEYtXIXGN7rLW22BeKAkK7NWFVQB5sgQDfulTBXTMRyRCukRah5Jzy88Nk8q77iSBvlDKpwbz9ODnSIZB+S+DZlBr5ABiGdkvjVW4vY4pkturAIStVU9LMERI1+IFxUEVS2hg9rvFsw8O0GVb+P0P5JWIH8EvQI8rTjOo0jbEm8OmrcXn+A/SRZ0ViQi
FKGLqlyXI3yUCGRP3kNZhw/Y1nZWyTPLp14sO1lNywcmAh1Xm4fl5aT6ie7S24bzYHY7GsmB/K5tMhJDublcqIU6szqA==
Received: from fsgaz.ro (SERVER-FSGAZ1 [127.0.0.1])
by mail.fsgaz.ro with ESMTPA
; Fri, 26 Jan 2018 17:05:42 +0200
MIME-Version: 1.0
X-Mailer: MailBee.NET 6.0.2.220
X-Priority: 3 (Normal)
From: admin@fsgaz.ro
To: check-auth@verifier.port25.com
Subject: test email
Date: Fri, 26 Jan 2018 17:05:42 +0200
X-Originating-IP: 95.77.149.71
Message-ID: <2.669fcfb7bdb080d42a52@SERVER-FSGAZ1>
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_BEB7_9BF727CF.A5C8F89D"
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
test
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<html><body>test</body></html>
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D--
Any suggestions would be appreciated.
Regards,
Adrian
