Re: RE: Need Assistance in SPF resolving error

Rasul,

In my book, the getspf2.py processor is buggy. It shouldn't be barfing 
on this highly subjective nonsense, dumb, 2 MX limit despite what it 
was controversially written in the latest specification.   That fell 
thru the crack and its too bad it was MISSED.

There is nothing wrong with your domain SPF record.  Can it be 
improved? Sure, like
move the IP4 checks to the beginning, leaving the higher overhead 
processing to last, but thats all subjective too.  This processor was 
apparently updated to RFC7208. The author of both.  But it is flawed 
because the RFC7208 recommendation is MUST DEFINITELY flawed. If I had 
saw that, it would of been challenged during SPF-BIS.

Any limit related to this should always be based on the REDUNDANCY of 
such operations and thats is only as LOCAL SPF DEPLOYMENT 
consideration.  That specs SHOULD of made that very clear.  2 limit? 
Come on.

In addition, the common limit from the old and new specs is 10, not 2. 
  So there is technical semantics "limits" ambiguity already with 
section 4.6.4 and 11.1.  2 limit?  Really?

Rasul, this SPF record is fine. If you own it, your only recourse is 
to MOVE the IP4 rules upfront before the MX checking is done.  But 
rest assure you are NOT the bug here - the GetSPF2.py is the bug and 
the author should seriously consider relaxing that 2 limit.  Odds are 
good he will be forced to do it some day when more reports come in and 
he gets tired of hearing about it. Blame others generally have an 
expiration date in the support world and this is one of them.  2 
limit? unbelievable.

-- 
Hector, Engineering & Technical Support
Santronics Software, Inc.
http://www.santronics.com (sales)
http://www.winserver.com (support)
http://www.winserver.com/AupInfo (Online AUP Help)
Office: 305-248-3204

On 7/24/2014 8:15 AM, Rasul Sharif .J via spf-discuss wrote:
> Hi,
>
> We are a small ISP firm and one of our client SPF record exist in our public DNS server and it was working fine but suddenly without making any changes in the SPF record we are receiving error in result while making SPF query in kitterman.com tool so Regarding to remove the below error, your assistance will  be highly appreciated.
>
> Checked link- http://www.kitterman.com/getspf2.py
>
> Results - PermError SPF Permanent Error: Void lookup limit of 2 exceeded
>
> But other tools I don't see any error.
>
> My client SPF record- v=spf1 mx ptr mx:mail.sasref.com.sa ip4:62.3.44.105 mx:mail2.sasref.com.sa ip4:62.3.44.100 -all
>
> Which point to domain name - sasref.com.sa
>
>
>
> Regards
>
> Rasul
>
>
>
>
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the addressee(s) named herein. If you are not the intended recipient or addressee, you should not use, disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of "Al Harbi Telecom" and or its units.
>
> Warning: Although reasonable precautions have been taken to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. If you have received this electronic mail message in error, please contact the sender directly
>
>
>
> -------------------------------------------
> Sender Policy Framework: http://www.openspf.net [http://www.openspf.net]
> Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
>
> Archives: https://www.listbox.com/member/archive/735/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/735/993478-34c23837
> Modify Your Subscription: https://www.listbox.com/member/?&
> Unsubscribe Now: https://www.listbox.com/unsubscribe/?&&post_id=20140724081600:3CEBB502-132C-11E4-8B67-820E63FA3163
> Powered by Listbox: http://www.listbox.com
>