[LINK] Now that's secure - I guess

[Scott Howard]

On Fri, Mar 30, 2012 at 10:06 PM, Noel Butler <noel.butler at ausics.net>wrote:

> If you do not like the restrictions (hey it *IS* their domain name you
> are using afterall), and given as you claim to have your own domains,
> why not use one of them, and configure SPF correctly, or since you
> disprove, perhaps with softfail or not at all, forwarding? well to your
> own domain one would hope one is clever enough to whitelist their own
> addresses - It's so simple even a child could understand it.
>


Sorry, but you're missing the point.

No sane ISP in the world should be configuring SPF hard fail for a customer
domain. It simply breaks far, far too much legitimate email.

Whether David has an alternative address he can use as a workaround or not
isn't relevant - Pacific Internet has screwed up here.  They seem to be
doing this for all of the customer domains, not just Hunterlink.

Despite it's flaws, SPF does have some valid use cases - even for hard
fail.  ISP customer domains with a hard fail (ie, -all) isn't one of them.

  Scott.