On Mon, 26 Jun 2006, Kurt Andersen wrote:
I was informed of a problem with the libspf-1.0 implementation today
by an external party who was rejecting mail from Agilent:
libspf-1.0 rejects a macro-expansion at the beginning
of a redirect line
. . .it appears SEVERAL SPF clients have
a problem with this and thusly reach your -all token.
Anyone else aware of problems with such a construct? My correspondent
reported the problem and a proposed patch to the libspf owners to fix
the problem.
I created a test case for this on pyspf. For my test case, at least, the
problem is not the macro, but the trailing dot in the redirect.
Allowing the trailing dot was a last minute addition to the spec.
Many implementations in the field do not handle it. Removing the trailing
dot from the test copy of the DNS data makes everything work fine.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com