Re: Wacky SPF Policy

>>> -----Q-ID----- --Size-- -Priority- ---Q-Time---
>>> --------Sender/Recipient-------- s15Dbwo2018764 250 1290946+Feb 5
>>> 08:37 <[email protected]> (Deferred: 453 Please see
>>> http://spf.pobox.com/[email protected]&ip=65.254.18.67)
>>> <[email protected]> (Deferred: 453 Please see
>>> http://spf.pobox.com/[email protected]&ip=65.254.18.67)
>>> s15DtnEW027481 501 1291256+Feb 5 08:55 <[email protected]> (Deferred: 453

> alex> Did I miss anything relevant from your message perhaps?
>
> The outbound queue I can see, with that failure message, is on VALID SPF
> SENDER of WPI.EDU messages.

Ahhh... wait....

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

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

http://www.openspf.org/Best_Practices/Checking_at_border_MTAs

There is nothing you can do about this, and nothing pobox can do about this.

> However, as a result of that bogus message, pobox has poisoned my email
> address, even if I send email from a valid, SPF-correct, sending system.

I think this did not happen.