-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Follow-ups to spf-devel@v2.listbox.com, please.
Roberto Alsina wrote:
> I had libspf2 1.2.5 installed, and was doing some plugins for qmail.
>
> So, I decided to do a SPF plugin.
>
> So, I go to www.libspf2.org and start reading about the API.
> Ok, so I get one of the patches (the postfix policyd to be exact) and
> decide to start hacking the code to make it work as a plugin.
>
> I rewrite, it's not much, it's 100 lines of code, a couple hours of
> work....
>
> And it doesn't build.
I'm no expert on libspf2, but if you're more specific, perhaps I or
somebody else can help.
> Is it me, or is the API documented in the website (and partly in the
> tarball, for example API still contains references to SPF_c_results_t)
> completely different from the API in the latest version the website has
> for download?
>
> I hacked the plugin together anyway by downloading the sources and
> pilfering code from spf_example, but... how often do these changes
> happen?
Changes to libspf2 don't happen very often anymore these days. libspf2
1.2.5 was released quite some time ago.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEKYERwL7PKlBZWjsRAn6hAJ9pbspcV2pHSHaLpah1kK/+TfpmwwCg6uBe
OTlz0z+zZYB1ZAM96U12fj4=
=EqgR
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Hash: SHA1
Follow-ups to spf-devel@v2.listbox.com, please.
Roberto Alsina wrote:
> I had libspf2 1.2.5 installed, and was doing some plugins for qmail.
>
> So, I decided to do a SPF plugin.
>
> So, I go to www.libspf2.org and start reading about the API.
> Ok, so I get one of the patches (the postfix policyd to be exact) and
> decide to start hacking the code to make it work as a plugin.
>
> I rewrite, it's not much, it's 100 lines of code, a couple hours of
> work....
>
> And it doesn't build.
I'm no expert on libspf2, but if you're more specific, perhaps I or
somebody else can help.
> Is it me, or is the API documented in the website (and partly in the
> tarball, for example API still contains references to SPF_c_results_t)
> completely different from the API in the latest version the website has
> for download?
>
> I hacked the plugin together anyway by downloading the sources and
> pilfering code from spf_example, but... how often do these changes
> happen?
Changes to libspf2 don't happen very often anymore these days. libspf2
1.2.5 was released quite some time ago.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEKYERwL7PKlBZWjsRAn6hAJ9pbspcV2pHSHaLpah1kK/+TfpmwwCg6uBe
OTlz0z+zZYB1ZAM96U12fj4=
=EqgR
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com