On 5/11/2004 7:43 AM, wayne sent forth electrons to convey:
As a result, I think it would be better for us to either not touch the
problem domain addressed by SPF, or to create a standard that is
(largely) compatible with the SPF install base.
How is the latter possible so long as derivatives of SPF are not
permitted by its authors?
Otherwise, I'd agree with you!
(The authors obstinate refusal has me thinking about possible
workarounds like: is the precedent that allowed spreadsheet software
clones that were keystroke-compatible allow us to copy SPF syntax?)