-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
alan premselaar wrote:
| as an ISP, you can't be platform biased either. you have to take into | account every possible mail client that anyone using your servers may | attempt to use. like it or not. | You are correct Alan, ISP's will have the toughest time getting to strict SPF. This is definitely a case where private domains with more control over their userbase need to lead the way.
For those of us with private domains, or running corporate domains, we have the easiest job. It is (among other things) a brand control issue. Your domain name is roughly equivalent to company letterhead, and should be protected. Any non-technological executives you may need to explain the situation to will understand the analogy, and you may find them more enthusiastic for a solution to the forgery problem than you are.
Just consider how the CEO would react if he discovered that someone was sending bomb threats to random people and companies around town on your company letterhead...
- -- Daniel Taylor VP Operations Vocal Laboratories, Inc. [EMAIL PROTECTED] http://www.vocalabs.com/ (952)941-6580x203 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBGhaX8/QSptFdBtURApAeAJ4yLSQM24lnFJo1solxulPxjSKu4QCeLmbK NtHAwDdLKf8t34kpNHnf3as= =I2pb -----END PGP SIGNATURE----- _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang