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
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=natthaphongr@absolute.co.th
DNS record(s):
absolute.co.th. 6400 IN TXT "v=spf1 a mx ptr -all"
absolute.co.th. 6400 IN A 61.47.18.102
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score: 0.4423]
2.1 AWL AWL: From: address is in the auto white-list
==========================================================
Explanation of the possible results (adapted from
draft-kucherawy-sender-auth-header-04.txt):
==========================================================
"pass"
the message passed the authentication test.
"fail"
the message failed the authentication test.
"softfail"
the message failed the authentication test, and the authentication
method has either an explicit or implicit policy which doesn't require
successful authentication of all messages from that domain.
"neutral"
the authentication method completed without errors, but was unable
to reach either a positive or a negative result about the message.
"temperror"
a temporary (recoverable) error occurred attempting to authenticate
the sender; either the process couldn't be completed locally, or
there was a temporary failure retrieving data required for the
authentication. A later retry may produce a more final result.
"permerror"
a permanent (unrecoverable) error occurred attempting to
authenticate the sender; either the process couldn't be completed
locally, or there was a permanent failure retrieving data required
for the authentication.
==========================================================
Original Email
==========================================================
Return-Path: <natthaphongr@absolute.co.th>
Received: from mail.absolute.co.th (61.47.18.102) by verifier.port25.com (PowerMTA(TM) v3.6a1) id hpfup00hse8b for <check-auth@verifier.port25.com>; Mon, 19 Apr 2010 02:51:57 -0400 (envelope-from <natthaphongr@absolute.co.th>)
Authentication-Results: verifier.port25.com smtp.mail=natthaphongr@absolute.co.th; mfrom=pass;
Authentication-Results: verifier.port25.com header.From=natthaphongr@absolute.co.th; domainkeys=neutral (message not signed);
Authentication-Results: verifier.port25.com; dkim=neutral (message not signed);
Authentication-Results: verifier.port25.com header.From=natthaphongr@absolute.co.th; pra=pass;
Received: from [127.0.0.1] ([125.24.40.39])
by mail.absolute.co.th
; Mon, 19 Apr 2010 15:54:31 +0700
Message-ID: <4BCC1A34.40001@absolute.co.th>
Date: Mon, 19 Apr 2010 15:54:12 +0700
From: Natthaphong Ruengpanyawut <natthaphongr@absolute.co.th>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: check-auth@verifier.port25.com
Subject: check auth please!
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hotmail/MSN won't automatically whitelist you after setting up the Sender-ID but it will surely be easier to spot the problem if you will want to track it up to exchanging emails with their support team. They have also a tool for self-support which I did not find it very useful but you may have a different result.
Anyway you should setup also DKIM, SPF and Domainkeys to be on the safe side with the rest , especially with yahoo! (domainkeys).
Apr 20, 2010 at 02:53 PM
your suggestion is very useful