I tried it on a third machine, and it's working there. The difference is
as follows. On the machine that fails, the long AOL SPF records are
being returned "malformed" and pyspf or its underlying support is
failing -- perhaps by design -- to trying again with TCP.
On the machine that fails (ldc1042), I get:
[EMAIL PROTECTED]:~$ host -t txt aol.com
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
aol.com descriptive text "v=spf1 ... ptr:mx.aol.com ?all"
aol.com descriptive text "spf2.0/pra ... ptr:mx.aol.com ?all"
On the machine that works (gx110), I get:
[EMAIL PROTECTED]:~$ host -t txt aol.com
;; Truncated, retrying in TCP mode.
aol.com descriptive text "spf2.0/pra ... ptr:mx.aol.com ?all"
aol.com descriptive text "v=spf1 ... ptr:mx.aol.com ?all"
with no "Warning: Message parser reports malformed message packet"
error. More importantly, I also get:
[EMAIL PROTECTED]:~$ python /usr/share/python-support/python-spf/spf.py
64.12.138.200 [EMAIL PROTECTED] imr-m06.mx.aol.com
('pass', 250, 'sender SPF authorized')
So now I need to figure out why my Hostway dedicated server would be
getting a malformed DNS response by UDP.
Thank you,
John
--
python-policyd-spf failing on AOL SPF records.
https://bugs.launchpad.net/bugs/205254
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
