-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ulrike vom Stein wrote:
As far as I know, none of the Windows/IIS/Exchange solutions are based
on libspf or libspf2, they all use proprietary SPF implementations
(which needn't be a bad thing).
Of course a proprietary implementation doesnt mean its a bad thing. In
fact I am afraid that I purchase a commercial solution which uses a
opensource/GNU library. I would not like it if a company makes profit
out of the hard work of the volunteers here. Somewhere in your list
archive I read for example that GFI purchased a solution which used
libspf. Such a solution would then no solution for me.
It should be either fully commercial OR fully opensource. Thats why I
would like to see small notes on your website which solution uses
which library.
Due to the very nature of closed-source commercial software it's difficult
to tell what library it uses if it is linked statically.
If anyone has reliable information about commercial products using open SPF
libraries, please submit it here. We can then add it to the website (for
better or worse).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFE7YnDwL7PKlBZWjsRAi+mAKDUb/ZC9CiPKDyub95+l4fofyVgjgCfYxvg
7VMQPSxZQCMgK2XkC+b8GG0=
=bAdh
-----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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com