-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Put a price tag on that. If you are selling a product, how many > dollars worth of orders are you willing to discard because the > potential customer sent a request for information through a > public access point instead of their own ISP?
If a potential customer sends you a message through a public access point and their domain has SPF enabled and doesn't list that access point as a valid relay, is that you fault? No, it's their administrator's fault for setting up restrictive SPF without properly configuring their employee's/user's laptops. Example: Let's say that I work for a hypothetical ACME Widgets, Inc. My e-mail address is [EMAIL PROTECTED] A potential customer, [EMAIL PROTECTED], tries to send me an e-mail message from his laptop using a public access point in his hotel. The network he's on is not listed as an allowed relay for example.com, according to their SPF record. My administrator (at acmewidgets.com) is honoring SPF records. What happens? If the people at example.com have setup their SPF record to say that mail from unlisted networks should be bounced, the message will be bounced. If they've said it should be subject to additional checks, but not outright rejected, it will be accepted and the SpamAssassin score increased. The behavior is exactly per their setup. Richard Laager Wikstrom Telecom Internet -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.2 Comment: If you don't know what this is, you can safely ignore it. iQA/AwUBQRkdsm31OrleHxvOEQKW+gCg09o78crSght3oPnLeNrkStYeSVoAoKRM ohcAK9K0LqS9HGqHRwinnVkc =xuhF -----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