At 02:18 AM 5/20/2005 -0500, wayne wrote:
In <5(_dot_)2(_dot_)1(_dot_)1(_dot_)0(_dot_)20050519132051(_dot_)04d6be08(_at_)pop(_dot_)mail(_dot_)yahoo(_dot_)com> David MacQuigg
<david_macquigg(_at_)yahoo(_dot_)com> writes:
> LOL. Good one. I do appreciate Bruce Lilly's comments, even though
> they are a PITA. The only problem is when I see him argue on one
> occasion that we must assume header order gets "randomized" as it
> crosses the Internet, and on another occasion, no change in header
> order is allowed. Seems like he picks his position just to be
> "negative".
Bruce is correct with both of these positions and they are not
controdictory. Despite the requirements in RFCs, there
implementations that are broken, either accidentally, or
deliberately.
Correct, and we should accommodate those implementations, if possible. But
in the protocol I am proposing, if a receiver is looking for the domain to
use in its lookup of domain ratings, it must trust the topmost headers, and
it must assume that a spammer will not be able to re-order the headers
added *after* the email crosses into the Trusted Forwarder region
surrounding his own domain. See http://purl.net/macquigg/email -
Forwarders.htm for an illustration of the region I am talking about.
< snip >
One thing that I will add is that I don't see things like CSV, DK or
IIM as "competition". They can go and get IETF standards if they
want, I don't care. Yeah, the HELO checking with CSV is basically
equivalent to the HELO checking with SPF, but the market can decide on
which is more useful.
I like this. Now if we could join up with these folks and propose a common
standard to the IETF, that might just get enough attention to make a few
headlines, and break the logjam. Can you think of anything we have in
common with them?
--
Dave
************************************************************ *
* David MacQuigg, PhD email: david_macquigg at yahoo.com * *
* IC Design Engineer phone: USA 520-721-4583 * * *
* Analog Design Methodologies * * *
* 9320 East Mikelyn Lane * * *
* VRS Consulting, P.C. Tucson, Arizona 85710 *
************************************************************ *