ViniciusLM
(usa Debian)
Enviado em 23/03/2012 - 16:40h
eritonalmeida escreveu:
Manda um e-mail para check-auth@verifier.port25.com ele retorna a pontuação e um diagnóstico do seu e-mail.
Então, eu já havia feito isso,
Ele retorna a seguinte mensagem
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: ns1.unimedsinop.com.br
Source IP: 189.53.236.82
mail-from: francisco@unimedsinop.com.br
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mailfrom=francisco@unimedsinop.com.br
DNS record(s):
unimedsinop.com.br. SPF (no records)
unimedsinop.com.br. 3600 IN TXT "v=spf1 ip4:189.53.236.80/29 -all"
----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: neutral (message not signed)
ID(s) verified: header.From=francisco@unimedsinop.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=francisco@unimedsinop.com.br
DNS record(s):
unimedsinop.com.br. SPF (no records)
unimedsinop.com.br. 3600 IN TXT "v=spf1 ip4:189.53.236.80/29 -all"
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)
Result: ham (-0.3 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
1.6 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 TVD_SPACE_RATIO TVD_SPACE_RATIO
==========================================================
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: <francisco@unimedsinop.com.br>
Received: from ns1.unimedsinop.com.br (189.53.236.82) by verifier.port25.com id hdj8k611u9ce for <check-auth@verifier.port25.com>; Fri, 23 Mar 2012 15:38:39 -0400 (envelope-from <francisco@unimedsinop.com.br>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=francisco@unimedsinop.com.br
Authentication-Results: verifier.port25.com; domainkeys=neutral (message not signed) header.From=francisco@unimedsinop.com.br
Authentication-Results: verifier.port25.com; dkim=neutral (message not signed)
Authentication-Results: verifier.port25.com; sender-id=pass header.From=francisco@unimedsinop.com.br
Received: by ns1.unimedsinop.com.br (Postfix, from userid 33)
id 567922AC4B4; Fri, 23 Mar 2012 10:36:12 -0400 (AMT)
To: <check-auth@verifier.port25.com>
Subject: (sem assunto)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 23 Mar 2012 10:36:12 -0400
From: francisco@unimedsinop.com.br
In-Reply-To: <0bd6e859f65933a995f2d5f8aa1ebba1@unimedsinop.com.br>
References: <32c65d7b37d16c54c51138cb08d469ce@unimedsinop.com.br>
<0bd6e859f65933a995f2d5f8aa1ebba1@unimedsinop.com.br>
Message-ID: <3893183d91b8d96deb307dff53a1626f@unimedsinop.com.br>
X-Sender: francisco@unimedsinop.com.br
User-Agent: Roundcube Webmail/0.7.1
Mas o problema é que ainda sou muito leigo nessa área de e-mail para entender.
