Read ahead, the real point is at the end of this message.
On Sun, Aug 01, 2004 at 03:33:49PM -0400, Michael Weiner wrote:
I find it hard to believe that after an entirely clean week of NOT being
on the list, and not reading any relevant emails to this regard (as i
was in the desert for a week purposely email-less), we are still in the
same spot we were several weeks ago.
Well, we did discuss some other things.
My point being, if people choose to use libspf2, thats certainly within
their prerogative - and getting support for said choice shouldnt be
difficult. However i believe many postings to this regard should NEVER
have made it to this list, but rather should be posted to the library
specific support list.
Actually, this all started with a posting on spf-help of someone who used the
windows implementation. As I had a libspf2 install i tried his problem
with libspf2, deduced that the problem was with the mixed case in helo
and dns. So this was _not_ a libspf2 post on spf-discuss. It was a
windows implementation (don't even know what it's called btw) on
spf-help that started it, and it was a valid concern.
I will also make one more possibly lame point, Requests For Comments
(RFCs) are just that, they are roadmaps NOT standards/laws and if people
can NOT see the difference and make that distinction, then there is a
real problem. I personally abhore implementors claiming that 'hey, i did
it according to the RFC, so it MUST be right' and things of that nature
- people, its a roadmap, not a hard and fast RULE or LAW.
Pleeaassee... RFC's are a good reference for implementors. The best
thing about them is that they're shared between all of the implementors.
Ah well, you yourself called it a lame point. Why i brought this up in
the first place, that the rfc said 'dont expect case to be preserved' is
that I noticed that sendmail does not preserve case, and this made
libspf f*ck *p when checking srs recipients. Which illustrates how
keeping to an rfc can help interoperability.
Lets get BACK to work and get this standardized such that implementors
and software providers can move on and complete the necessary work they
need to do to get this out into the wild and as fully implemented as we
can.
As you may have noticed, it did get standardized: compare domains
in an case-insensitive manner. There. Period. Did you read the thread?
Or just the last bit of it, where it got nasty?
Now if this goes on any longer, i _will_ volunteer to moderate this
list. There's _way_ too much crap on these lists lately.
Koen
--
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, embedded systems, unix expertise, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Send us money! http://spf.pobox.com/donations.html
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
pgp3wS7159UEB.pgp
Description: PGP signature