21 Jul
2010
21 Jul
'10
11:46 a.m.
Although many SPF failures are due to sender misconfiguration, this can also happen due to a misconfiguration on the receiver's part. Looking at your original message again, the headers would suggest that this might be the case here; the receiver might not be checking SPF at the border, but rather one or more mail hops further inside their network. See the first item at http://www.openspf.org/FAQ/Common_receiver_mistakes
This is the scenario I am seeing. On reflection my summarized version of events in the original email was poorly constructed... Anyway, I'm running into this problem a lot lately and almost at the point of ditching SPF entirely because of it. The "cons" - admin problems - seem to outweigh the "pros" so far.