Re: Wacky SPF Policy

>>>>> "alex" == Alex van den Bogaerdt <[email protected]> writes:

alex> You are not sending to pobox, you are sending to eastmeadow.k12.ny.us

Yes, this was my misunderstanding.  When they declined the message with the
pobox url, I thought pobox was involved.

alex> The problem is there; apparently they are relaying the message internally
alex> and then use the IP address of the relay to check against your SPF
alex> policy.  Pobox is only used to synthesize the message, the message is
alex> generated by, and delivered to you by, eastmeadow.k12.ny.us

Ah.  They give a pobox URL, describing the failure, but the pobox url will
construct a message based on its arguments, as you say...  So, I should calm
down, it's not about me at all.

You're guessing that eastmeadow has an internal IP of that address.  The IP
they reference is 65.254.18.67, named
host-65-254-18-67.static.longislandfiberexchange.net, but their edge MX is
76.12.176.181, which is somewhat different.  Of course, I have no clue about
their architecture.

I should have looked about whether Eastmeadow, NY is on Long Island.  Guess
what?  It is.  The eastmeadow/longislandfiber linkage seems very likely as you
suggest.

I'm all upset for no reason.  Also, I guess they're not getting mail from
anybody with SPF, but that's their issue.