-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dan,
you wrote:
Thanks to your suggestions, I have now been able to rewrite our E-card
service so that it is compliant with SPF. It seems to be going through
the SPF as stated by one of our complaining customer.
Glad to hear that!
If you would be willing to add it to the SPF-compliant E-card services,
I would be pleased.
We aren't listing all kinds of services that are SPF compliant because the
list would eventually grow huge, and also those services' target audiences
wouldn't be looking at that list anyway.
I have even been considering us stopping listing SPF-enabled proprietary
products[1] because the list is going to get too long as SPF support
becomes common.
It was quite combersome, because I had to handle the bounces back, which
is all that is difficult when we change the sender address. This is very
important, else people won't know that their e-card was not received. I
had to scratch my head some hours to be able to make it work the right
way, but using sendmail and smrsh I finally got it with a php script.
Glad you got it to work.
References:
1. http://www.openspf.org/Implementations
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGMloEwL7PKlBZWjsRAvXXAKCHhFXaKfuEW9izkq3Ty8BIjVKBBgCgxcfS
jZ6qDB3/K5gfNDdRvM+Zxr0=
=JRra
-----END PGP SIGNATURE-----
-------------------------------------------
-----------------------------------------------------------------------
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/?list_id=735
Powered by Listbox: http://www.listbox.com