----- Original Message -----
From: "william(at)elan.net" <william(_at_)elan(_dot_)net>
It is improper for you to make an assumption that you know
what administrator wants better then that administrator and
that you're smarter and/or can write smarter software.
There is a feedback loop that clearly exists (must
exist for software to be successful).
Who deals with more administrators, You, an Administrator? Or an software
vendor with thousands of customers? Sorry, I believe I have a better feel
for the general scope and operation on a global scale than you do.
I make no statement about being SMARTER software or better software, but god
damn it, I do have a darn good handle of WHAT the issues are from an
AUTOMATED SMTP CLIENT/SERVER system. I have to make sure it works for
people like you and people not like you. I have to make sure it follows the
STANDARDS and BCP. Any SMTP software that makes a HELO A match a
REQUIREMENT out of the box is BROKEN according to standards.
Sorry, I disagree. There is a MUST NOT reject on a HELO A mismatch only
concept.
Yet, as I said, if you CHOOSE to disrespect this, then your LOCAL policy
only. It is not a STANDARD policy.
I'm sure, you don't see this.
But is is still that way too many times I see bad and non-compliant
software that admins have to deal with.
And even THEN when MODERN software, you STILL have sysops who don't
configure their system right in regards to the client domain name.
A MUST NOT rejection is the STATUS QUO.
So why are you arguing a fact of life?
Are you saying it is true? That it isn't true any more? I doubt you will
bring this up in any IETF SMTP related forum.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
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