At 02:36 PM 4/4/2005 -0700, you wrote:
At 02:30 PM 04/04/2005, you wrote:
So, how does one go about getting big lazy corps to fix serious email
problems?
Stop doing business with them and make sure they know why. They have
no incentive to get their act together until it effects their bottom line.
And if all five of us do that, we might really get Blockbuster's attention. :>)
This is a problem SPF is going to continue having, and not just with
Blockbuster. Other methods have similar problems - CSV insists that the
HELO name be properly set up, with special SRV records, etc. Imagine the
sysadmin at Blockbuster trying to decide whether to use CSV, SPF, SenderID,
DomainKeys, ... It's no wonder the world is ignoring email authentication.
I suggest we give senders the option of declaring any identity they
please. If they chose to use the HELO or MAIL FROM identity, they can do
that by adding a flag *ID* just after the name they want to declare. If
they want something else, they can add a string ID=<name> to either the
HELO or MAIL FROM commands.
It's trivia like this that add five months delay to the universal adoption
of email authentication.
-- Dave
************************************************************ *
* David MacQuigg, PhD email: dmquigg-spf 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 *
************************************************************ *