On Fri, 2005-06-17 at 10:55 +0200, Per Jessen wrote:
> Hi,
>
> I've just now joined the list hoping to find out if the build issues in 1.2.5 (as mentioned by
> "richs at whidbey") have been resolved?
>
> I'm trying to build policyd-1.0.1 which fails on not finding spf2/spf.h, in spite of this being
> perfectly well installed.
In several of your emails you refer to my library (libspf) when you are
indeed referring to another library. This is obviously because of the
incredibly poor choice made by the author of the library formerly known
as libspf-alt.
Please be careful to appropriately reference the correct name in future.
If you find your self wondering more about this issue see the list
archives of SPF-DISCUSS and SPF-DEVEL for my extremely vocal objections
to the ambiguous, confusing and generally misleading naming convention
present with 'libspf2' and 'libsrs2'.
Please do not reply to this message as it is not intended to evoke a
response. If a response is warranted please post it offlist as I am not
looking to bring this issue back from the dead other than to point out
that its important to be very clear about which library you reference
especially when referring to bugs as its potentially misleading and
confusing to developers and users alike.
Thank you in advance.
Cheers,
James
--
James Couzens,
Programmer
http://libspf.org - ANSI C Sender Policy Framework library
http://ses.codeshare.ca - Signed Envelope Sender, A comprehensive
and simple solution to stopping SMTP forgery. Please review our
work and find any flaws in our protocol.
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
> Hi,
>
> I've just now joined the list hoping to find out if the build issues in 1.2.5 (as mentioned by
> "richs at whidbey") have been resolved?
>
> I'm trying to build policyd-1.0.1 which fails on not finding spf2/spf.h, in spite of this being
> perfectly well installed.
In several of your emails you refer to my library (libspf) when you are
indeed referring to another library. This is obviously because of the
incredibly poor choice made by the author of the library formerly known
as libspf-alt.
Please be careful to appropriately reference the correct name in future.
If you find your self wondering more about this issue see the list
archives of SPF-DISCUSS and SPF-DEVEL for my extremely vocal objections
to the ambiguous, confusing and generally misleading naming convention
present with 'libspf2' and 'libsrs2'.
Please do not reply to this message as it is not intended to evoke a
response. If a response is warranted please post it offlist as I am not
looking to bring this issue back from the dead other than to point out
that its important to be very clear about which library you reference
especially when referring to bugs as its potentially misleading and
confusing to developers and users alike.
Thank you in advance.
Cheers,
James
--
James Couzens,
Programmer
http://libspf.org - ANSI C Sender Policy Framework library
http://ses.codeshare.ca - Signed Envelope Sender, A comprehensive
and simple solution to stopping SMTP forgery. Please review our
work and find any flaws in our protocol.
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
Attached Files:
-
signature.asc (0.18 KB)