E-mails caindo na caixa de Spam

1. E-mails caindo na caixa de Spam

Alexandre Michael de Jesus Castro
ZeTeta

(usa Linux Mint)

Enviado em 06/03/2019 - 17:48h

Galera, boa tarde.. Na empresa onde trabalho estou configurando um servidor de e-mail Zimbra, so que estou com um problema. Todo tipo de e-mail que envio para o Gmail estão caindo na caixa de spam, ja fiz todo tipo de configuração, DKIM, DMARC, SPF, rDNS etc... Esta aparentemente tudo ok. Usei alguns sites para testar a pontuação do meu e-mail, https://www.mail-tester.com/ nesse site a pontuação foi de 10/10, usei site para vê se meu ip esta em uma blacklist e não esta em nenhuma. Ai não sei oq eu preciso fazer para poder identificar o problema. O servidor esta recem configurado e esta hospedado na Amazon.
Meu ip: 18.225.15.188
Meu dominio: sdredes.com

Por fim eu enviei um e-mail para o endereço auth-results@verifier.port25.com e ele me retornou isso:

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: sdmail.sdredes.com
Source IP: 18.225.15.188
mail-from: zimbra@sdredes.com

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mailfrom=zimbra@sdredes.com

DNS record(s):
sdredes.com. 60 IN TXT "v=spf1 a mx a:sdmail.sdredes.com ip4:18.225.15.188 ~all"
sdredes.com. A (no records)
sdredes.com. 60 IN MX 10 sdmail.sdredes.com.
sdmail.sdredes.com. 60 IN A 18.225.15.188


----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result: pass (matches sdmail.sdredes.com)
ID(s) verified: policy.iprev=18.225.15.188

DNS record(s):
188.15.225.18.in-addr.arpa. 60 IN PTR sdmail.sdredes.com.
sdmail.sdredes.com. 60 IN A 18.225.15.188


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass (matches From: zimbra@sdredes.com)
ID(s) verified: header.d=sdredes.com

Canonicalized Headers:
date:Wed,'20'6'20'Mar'20'2019'20'18:57:50'20'+0000'20'(UTC)'0D''0A'
from:E-mail'20'Zimbra'20'<zimbra@sdredes.com>'0D''0A'
to:check-auth@verifier.port25.com'0D''0A'
message-id:<1989191565.50.1551898670599.JavaMail.zimbra@sdredes.com>'0D''0A'
mime-version:1.0'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=sdredes.com;'20's=sdredesdkim;'20't=1551898670;'20'bh=nRhRFnTGApqjQ+apAlusbmfgmM948NOhEyWoKLJm00c=;'20'h=Date:From:To:Message-ID:MIME-Version;'20'b=

Canonicalized Body:
--=_72c5b161-e432-4424-8848-0c992f2805e1'0D''0A'
Content-Type:'20'text/plain;'20'charset=utf-8'0D''0A'
Content-Transfer-Encoding:'20'7bit'0D''0A'
'0D''0A'
teste'0D''0A'
'0D''0A'
--=_72c5b161-e432-4424-8848-0c992f2805e1'0D''0A'
Content-Type:'20'text/html;'20'charset=utf-8'0D''0A'
Content-Transfer-Encoding:'20'7bit'0D''0A'
'0D''0A'
<html><body><div'20'style="font-family:'20'arial,'20'helvetica,'20'sans-serif;'20'font-size:'20'12pt;'20'color:'20'#000000"><div>teste</div></div></body></html>'0D''0A'
--=_72c5b161-e432-4424-8848-0c992f2805e1--'0D''0A'


DNS record(s):
sdredesdkim._domainkey.sdredes.com. 60 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArV+Pkh+it6pmKOh20HrkXm9mOMDWmTZlWDwydsSylu6GHzVUjO9Fbt9PgjpLLJ6GFPmQYA0aP7Ih1Xt10vvKBWpQ2uMFebUDhTdcK/ThqNTkjMAu4wDoTQ3qef0tiogWZT2HsgwlispbWTnBlM3lJrqri9b/nGphZqR8nS+exv6wkCRHsT9h+1sZ/DzZEDGzwCRyL6f26nJMmnuZf60s2MdS12uK7KsFxZsgfvg9jHquwGFDhT4t/oH7CmvFuwGyYvGxzYes7lwVRyEjNlWuUvxAsVPdCK35SEm4Pd+n1BfxN66Ov/sGkfgZvTUv2WdLoMUoTo+WpziY9LRbFggg4wIDAQAB"

Public key used for verification: sdredesdkim._domainkey.sdredes.com (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.0 (2014-02-07)

Result: ham (-2.0 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.0 SPF_PASS SPF: sender matches SPF record
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_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid



==============================================================
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: <zimbra@sdredes.com>
Received: from sdmail.sdredes.com (18.225.15.188) by verifier.port25.com id hg0c322e8s4g for <check-auth@verifier.port25.com>; Wed, 6 Mar 2019 18:57:53 +0000 (envelope-from <zimbra@sdredes.com>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=zimbra@sdredes.com;
iprev=pass (matches sdmail.sdredes.com) policy.iprev=18.225.15.188;
dkim=pass (matches From: zimbra@sdredes.com) header.d=sdredes.com
Received: from localhost (localhost [127.0.0.1])
by sdmail.sdredes.com (Postfix) with ESMTP id 35308BF063
for <check-auth@verifier.port25.com>; Wed, 6 Mar 2019 18:57:51 +0000 (UTC)
Received: from sdmail.sdredes.com ([127.0.0.1])
by localhost (sdmail.sdredes.com [127.0.0.1]) (amavisd-new, port 10032)
with ESMTP id hoAVwVgNGUED for <check-auth@verifier.port25.com>;
Wed, 6 Mar 2019 18:57:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by sdmail.sdredes.com (Postfix) with ESMTP id CD7F0BF064
for <check-auth@verifier.port25.com>; Wed, 6 Mar 2019 18:57:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 sdmail.sdredes.com CD7F0BF064
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdredes.com;
s=sdredesdkim; t=1551898670;
bh=nRhRFnTGApqjQ+apAlusbmfgmM948NOhEyWoKLJm00c=;
h=Date:From:To:Message-ID:MIME-Version;
b=HqTAcJ/apAlDh9PJfmCBPwwnWScoC/cpYXoO4M6yVnHKIOiNmDaYfNE/oJ27Ye5sS
PZk/q11H61FHilT64D4LdPCGP/fFT3W8thPhvC3ocTQE5rzr/LhFtygeDQnQekR1rF
kiZ3+3LPLuAVwP968mAJtCoiumi6niD8mE37ZQ0QuYa8nKzwli7GkWR92mlKYAfU85
o3bw5LUCgH/f87SnyvL/VWMKFkqECQ7q2CRXsSHzFqy851dUueOmIdhDzSKEDu2SjS
5JskIiHoBzkPqJ9iMV/s3jS/oBBH+0tKswJZ+UmDE+5MLCsIpsZ6mgsD8A1efNtEg1
dxbrkFFpQphrg==
X-Virus-Scanned: amavisd-new at sdredes.com
Received: from sdmail.sdredes.com ([127.0.0.1])
by localhost (sdmail.sdredes.com [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id iYh6waph63_K for <check-auth@verifier.port25.com>;
Wed, 6 Mar 2019 18:57:50 +0000 (UTC)
Received: from sdmail.sdredes.com (sdmail.sdredes.com [172.31.6.129])
by sdmail.sdredes.com (Postfix) with ESMTP id B11ADBF063
for <check-auth@verifier.port25.com>; Wed, 6 Mar 2019 18:57:50 +0000 (UTC)
Date: Wed, 6 Mar 2019 18:57:50 +0000 (UTC)
From: E-mail Zimbra <zimbra@sdredes.com>
To: check-auth@verifier.port25.com
Message-ID: <1989191565.50.1551898670599.JavaMail.zimbra@sdredes.com>
Subject: =?utf-8?Q?testando_pontua=C3=A7=C3=A3o?=
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=_72c5b161-e432-4424-8848-0c992f2805e1"
X-Originating-IP: [172.31.6.129]
X-Mailer: Zimbra 8.8.11_GA_3780 (ZimbraWebClient - GC72 (Win)/8.8.11_GA_3780)
Thread-Index: /UtT+SSJwPE78zGmIKVKhizgEv5zuA==
Thread-Topic: testando =?utf-8?B?cG9udHVhw6fDo28=?=

--=_72c5b161-e432-4424-8848-0c992f2805e1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

teste

--=_72c5b161-e432-4424-8848-0c992f2805e1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>teste</div></div></body></html>
--=_72c5b161-e432-4424-8848-0c992f2805e1--