caindo no spam por favor URGENTE
1. caindo no spam por favor URGENTE
java-man
(usa Outra)
Enviado em 25/04/2012 - 20:07h
Recebi uma carta do registro.br que fala para alterar a porta do smtp para 587 eu hoje utilizo a 25 deve ser por isso que minhas mensagens chega no SPAM de alguns provedores e também do hotmail?Já verifiquei e meu IP parece que está tudo ok nas autoridades certificadoras.
já havia colocado no meu DNS o SPF pois sei que isto também influencia nos provedores para distinguir se é SPAM ou não.
Meu DNS utilizo este SPF que é v=spf1 ptr ip4:000.00.000.00 mx:mail.dominio.com.br ~all no lugar do 0 o meu ip.
Alguém me ajuda, preciso resolver isto.
Também enviei um e-mail para check-auth@verifier.port25.com ele retornou a seguinte mensagem, alguém me ajuda a analisar, porfavor URGENTE!
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
DomainKeys check: neutral
DKIM check: neutral
Sender-ID check: pass
SpamAssassin check: ham
==========================================================
Details:
==========================================================
HELO hostname: mail.solustore.com.br
Source IP: 201.86.139.70
mail-from: hugo@solustore.com.br
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mailfrom=hugo@solustore.com.br
DNS record(s):
solustore.com.br. SPF (no records)
solustore.com.br. 3600 IN TXT "v=spf1 ptr ip4:201.86.139.70 mx:mail.solustore.com.br ~all "
70.139.86.201.in-addr.arpa. 43200 IN PTR 201.86.139.70.static.gvt.net.br.
201.86.139.70.static.gvt.net.br. 86400 IN A 201.86.139.70
----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: neutral (message not signed)
ID(s) verified: header.From=hugo@solustore.com.br
DNS record(s):
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: neutral (message not signed)
ID(s) verified:
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.
----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=hugo@solustore.com.br
DNS record(s):
solustore.com.br. SPF (no records)
solustore.com.br. 3600 IN TXT "v=spf1 ptr ip4:201.86.139.70 mx:mail.solustore.com.br ~all "
70.139.86.201.in-addr.arpa. 43200 IN PTR 201.86.139.70.static.gvt.net.br.
201.86.139.70.static.gvt.net.br. 86400 IN A 201.86.139.70
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)
Result: ham (0.8 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.4 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
0.0 HTML_MESSAGE BODY: HTML included in message
2.3 EMPTY_MESSAGE Message appears to have no textual parts and no
Subject: text
==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================
SPF and Sender-ID Results
=========================
"none"
No policy records were published at the sender's DNS domain.
"neutral"
The sender's ADMD has asserted that it cannot or does not
want to assert whether or not the sending IP address is authorized
to send mail using the sender's DNS domain.
"pass"
The client is authorized by the sender's ADMD to inject or
relay mail on behalf of the sender's DNS domain.
"policy"
The client is authorized to inject or relay mail on behalf
of the sender's DNS domain according to the authentication
method's algorithm, but local policy dictates that the result is
unacceptable.
"fail"
This client is explicitly not authorized to inject or
relay mail using the sender's DNS domain.
"softfail"
The sender's ADMD believes the client was not authorized
to inject or relay mail using the sender's DNS domain, but is
unwilling to make a strong assertion to that effect.
"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 policy record from DNS. 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 or
a syntax error in a retrieved DNS TXT record. A later attempt is
unlikely to produce a final result.
DKIM and DomainKeys Results
===========================
"none"
The message was not signed.
"pass"
The message was signed, the signature or signatures were
acceptable to the verifier, and the signature(s) passed
verification tests.
"fail"
The message was signed and the signature or signatures were
acceptable to the verifier, but they failed the verification
test(s).
"policy"
The message was signed but the signature or signatures were
not acceptable to the verifier.
"neutral"
The message was signed but the signature or signatures
contained syntax errors or were not otherwise able to be
processed. This result SHOULD also be 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.
==========================================================
Original Email
==========================================================
Return-Path: <hugo@solustore.com.br>
Received: from mail.solustore.com.br (201.86.139.70) by verifier.port25.com id hj1vga11u9ct for <check-auth@verifier.port25.com>; Wed, 25 Apr 2012 18:47:33 -0400 (envelope-from <hugo@solustore.com.br>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=hugo@solustore.com.br
Authentication-Results: verifier.port25.com; domainkeys=neutral (message not signed) header.From=hugo@solustore.com.br
Authentication-Results: verifier.port25.com; dkim=neutral (message not signed)
Authentication-Results: verifier.port25.com; sender-id=pass header.From=hugo@solustore.com.br
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.solustore.com.br (Postfix) with ESMTP id DD8AE1E63DB
for <check-auth@verifier.port25.com>; Wed, 25 Apr 2012 19:46:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at solustore.com.br
Received: from mail.solustore.com.br ([127.0.0.1])
by localhost (mail.solustore.com.br [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id Dw8eBsgK4-NI for <check-auth@verifier.port25.com>;
Wed, 25 Apr 2012 19:46:23 -0400 (EDT)
Received: from mail.solustore.com.br (mail.solustore.com.br [192.168.1.3])
by mail.solustore.com.br (Postfix) with ESMTP id 5D1201E63D1
for <check-auth@verifier.port25.com>; Wed, 25 Apr 2012 19:46:23 -0400 (EDT)
Date: Wed, 25 Apr 2012 19:46:23 -0400 (EDT)
From: Hugo Rodrigues <hugo@solustore.com.br>
To: check-auth@verifier.port25.com
Message-ID: <2172090.775.1335397583022.JavaMail.root@mail.solustore.com.br>
Subject:
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_774_6245042.1335397583016"
X-Originating-IP: [201.86.139.70]
X-Mailer: Zimbra 7.1.4_GA_2555 (ZimbraWebClient - FF3.0 (Win)/7.1.4_GA_2555)
------=_Part_774_6245042.1335397583016
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
------=_Part_774_6245042.1335397583016
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'><br></div></body></html>
------=_Part_774_6245042.1335397583016--
Algém me ajuda? qualquer domínio configurado neste ZIMBRA cai como SPAM.