incorrect Received-SPF format

All this time, I've been generating Received-SPF header fields, and I've 
been doing it wrong.  I was just emulating what I've seen elsewhere, but just
got through checking RFC4408 :-(  Here is what I output currently:

2007Mar26 21:37:14 [8573] Received-SPF: permerror include:sbcglobal.net
	(mail.bmsi.com: permanent error in processing domain of barbara.com: No
	valid SPF record for included domain: sbcglobal.net)
	client_ip=210.213.146.37; envelope_from="[email protected]";
	helo=localhost.localdomain; receiver=mail.bmsi.com;
	problem="include:sbcglobal.net"; mechanism=~all; identity=mailfrom

Putting the problem mechanism after the result is no longer allowed
in RFC4408.  I'm pretty sure it was there in earlier drafts.  Furthermore,
the spec requires camel case capitalization (provides literals for
result).  So, it should look like this instead:

2007Mar26 21:37:14 [8573] Received-SPF: PermError (mail.bmsi.com: permanent
	error in processing domain of barbara.com: No valid SPF record for
	included domain: sbcglobal.net) client_ip=210.213.146.37;
	envelope_from="[email protected]"; helo=localhost.localdomain;
	receiver=mail.bmsi.com; problem="include:sbcglobal.net";
	mechanism=~all; identity=mailfrom

But I guess the parser I'm about to write should be able to handle the old 
way also.

-- 
	      Stuart D. Gathman <[email protected]>
    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.


-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007