> I realize that it is malformed - shouldn't have non FQDN's in the a: or
> mx: types, and male.example.com doesn't have an mx record (it is the mx
> for 'example.com').  But that being said, those ones that are valid
> ought to be recognized.
> 
A gentle suggestion to the SPF owner to visit 

http://www.kitterman.com/spf/validate.html

to validate and fix his SPF record might help both him and you.


Martin


Reply via email to