-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Les Mikesell wrote: | On Tue, 2004-08-10 at 14:10, Richard Laager wrote: | | |>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. | | | How would this work for wireless delivery services like Blackberry? | My CEO has one of these and uses it a lot. All messages must | be sent through their server but we want the 'From:' to be | his desktop address. | SPF Classic doesn't check From:, so the SPF classic record would be Blackberry's since it came from their server and would have their MAIL FROM attached to it.
For the Marid record you would set ?include:{Blackberry's domain}
to reflect the fact that e-mail from that domain claiming to
be from you may or may not be authorized.
- -- 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
iD4DBQFBGhSV8/QSptFdBtURAoRZAJimNJ4uss9JM8ff0/FNBUns74FHAJ9mm2MY w7lcnkJVkw62XA/pYGghVg== =115Z -----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
