bigpond
Australian telecommunications provider Telstra has very recently implemented a “p=reject” DMARC policy for their primary email domains (telstra.com, telstra.com.au, bigpond.com and bigpond.com.au). What this means for senders is that it is no longer safe to use these domains in your from address when sending from anything other than Telstra’s email platform. No using Telstra email addresses to send mail from your ESP, CRM or newsletter platform — these domains are now configured so that ISPs are encouraged to reject mail from these domains when not authenticated properly.Remember that in this day in age it’s always best to send your emails from a third party platform using only your own specific domain or subdomain, owned by you and configured to authenticate properly from every email sending platform you’re using.My cached DMARC checks for the top 10 million domains show Telstra domains previously had a DMARC policy of “none” back in June
Australian telecommunications provider Telstra has long provided internet services (including email), initially via the “Bigpond” brand (launched in 1996, later retired). They’re reported to have 18.8 million customer accounts, though I don’t know how many active email accounts that translates to. Even if you assume a 1:1 correlation between user accounts and email accounts (which is unlikely), that’s still quite a bit smaller than, say, Yahoo Mail (which was reported as having 225 million active users as of 2017). Regardless, a multi-million subscriber base is nothing to sneeze at.I don’t have much information on blocking/unblocking information for senders with Telstra/Bigpond delivery issues at this time. I’ll add information here as I’m able to.In the mean time, if you are having a Telstra/Bigpond-related deliverability issue, and if you would like to segment out or suppress mail to the Telstra domains, here’s a list of their primary email domains:telstra.comtelstra.com.aubigpond.combigpond.com.auTelstra hosts email for