-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roberto Alsina wrote:
I would suggest you look into this and make sure you have things the
way you want. If I were to hazard a non-lawyer guess, if you use excc
you will have to license the package as a whole under GPL (which I
think you can do).
AFAIK, right now this is not really a problem. My own RaSPF code is
under Python license, and the whole is GPL. I will se what I can do to
make it stay under a more liberal license (even if it means replacing
excc).
I don't see a real problem with GPL, but for the sake of SPF proliferation,
BSD would probably be best.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFF+W6OwL7PKlBZWjsRAtYhAKDfQbm2AcS/jkb/FUOJwB/EAhNVqACg8qjR
wiAaE/59Syharti1t5K/ZQg=
=Vi/V
-----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