Hector, Sender-ID needs 822 headers to work.
On Thu, 2005-06-23 at 16:06 -0400, Hector Santos wrote:
I created a hotmail test account to check this out.
Its dropping mail that doesn't have any RFC 2822 headers. Just goes into
La-La land! It should atleast use the 2821 fields to set the To: and From:.
A clear break away from common practice.
I just created a message via my winserver.com server using an authenticated
session so I can route it
Mail From: foobar(_at_)foobarxyz(_dot_)com
Rcpt to: hls70(_at_)hotmail(_dot_)com
Mail From: foobar(_at_)foobarxyz(_dot_)com
Rcpt to: hls70(_at_)hotmail(_dot_)com
I got it at hotmail with no warning of any kind....
MIME-Version: 1.0
Received: from winserver.com
([208.247.131.9]) by mc3-f38.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211);
Thu, 23 Jun 2005 12:38:56 -0700
Received: by winserver.com (Wildcat! SMTP Router v6.1.451.4)
for hls70(_at_)hotmail(_dot_)com; Thu, 23 Jun 2005 15:40:19 -0400
Received: from ([65.10.60.163]) HELO=hdev1
by winserver.com (Wildcat! SMTP v6.1.451.4)
with SMTP id 3307651640; Thu, 23 Jun 2005 15:40:18 -0400
X-Message-Info: JGTYoYF78jE8h9KXRWfSX+RRchoWFWtTKyLNj8FiCHk=
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Return-Path: foobar(_at_)foobarxyz(_dot_)com
X-OriginalArrivalTime: 23 Jun 2005 19:38:57.0395
(UTC) FILETIME=[325F2430:01C5782B]
I think the above is spoofing if you ask me!
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
----- Original Message -----
From: "Scott Kitterman" <spf2(_at_)kitterman(_dot_)com>
I tried it for Pass, Neutral and Fail scenarios.
Pass and Neutral said nothing about SenderID.
Fail said:
The sender of this message, spf2(_at_)kitterman(_dot_)com, could not be
verified by
Sender ID. Learn more about Sender ID.
Text at the learn more... link is:
"About Sender ID
Sender ID is an initiative championed by Microsoft and other industry
leaders as a technical solution to help counter spoofing, which is the
primary deceptive practice used by spammers.
E-mail domain spoofing involves forging a sender's address on e-mail
messages. It can be used by malicious individuals to mislead e-mail
recipients into reading and responding to deceptive mail. These phony
messages can jeopardize the online safety of the user and damage the
reputation of the company purported to have sent the message. Spoofed
e-mail
often contains "phishing" scams. In such ploys, a spammer, posing as a
trusted party such as a bank or reputable online vendor, sends millions of
e-mail messages directing recipients to websites that appear to be
official
but are in reality scams. Visitors to these fraudulent websites are asked
to
disclose personal information, such as credit card numbers, or to purchase
counterfeit or pirated products.
Sender ID seeks to verify that every e-mail message originates from the
Internet domain from which it claims to have been sent. This is
accomplished
by checking the address of the server sending the mail against a
registered
list of servers that the domain owner or e-mail recipient have allowed to
send e-mail. This comparison is automatically performed by the Internet
service provider (ISP) or recipient's e-mail server before the e-mail
message is delivered. If the Sender ID verification passes, the message is
delivered as regular mail. If the check fails, the message is further
analyzed and may be refused by the receiving server, or flagged to the
user
as a possible deceptive message. Depending on the recipient's ISP or
e-mail
server software, messages that fail the Sender ID check may be flagged and
sorted differently. For example, a simple icon may be displayed in the
message to indicate the failure; the message may be sent to the junk mail
folder for the recipient's review, or it may be automatically rejected and
deleted.
There is no single solution to stopping all spam and online fraud. Rather,
Sender ID is a significant first step that many in the industry are
supporting to counter spam and online phishing attacks. "
I don't have a SoftFail domain to try right now.
Scott K
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Read the whitepaper! http://spf.pobox.com/whitepaper.pdf
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Read the whitepaper! http://spf.pobox.com/whitepaper.pdf
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
--
:: Jeff Macdonald | Principal Engineer, Messaging Technologies
:: e-Dialog | jmacdonald(_at_)e-dialog(_dot_)com
:: 131 Hartwell Ave. | Lexington, MA 02421
:: v: 781-372-1922 | f: 781-863-8118
:: www.e-dialog.com