Is Telstra SPAM filtering delaying my legitimate email?

For the past few months, I have had many of my emails delayed by anything from a couple of minutes to 12 hours.  This used to be sporadic, but is happening pretty much all of the time now.

As background, I've used a ,name (dotname) email address, provided to me by Melbourne IT, since 2004, to provide an 'address for life'. This is uncommon, as it is a third level domain fname.lname.name, which comes with email forwarding to fname@lname.name, which I configure via the Melbourne IT interface.  I have successfully had all of my email sent to this address, which is then forwarded seemlessly to my BigPond address (or occassionly optusnet) over the last 13 years.

I believe these delays (and possibly rejections) started happening when Telstra started looking at 

Sender Policy Framework (SPF) Records. It seems that now if something is coming to my bigpond address, it sees that it is coming via a .name mx server. not the original sender's server, and it gets a Received-SPF: fail, or sometimes a Received-SPF: softfail.

From what I can see, this happens with whatever .name server initially receives my mail on the way through - mx01.nic.name, mx02.nic.name, mx03.nic.name etc.

Here's an example from today (with my BigPond address changed to myaddress.com and my email address changed to fname@lname.name.

Return-Path: <delivery@mx.sailthru.com>
Received: from extmail.bigpond.com ([10.10.24.4])
          by nsstlfep04p-svc.bpe.nexus.telstra.com.au with ESMTP
          id <20170428033004.RJVL791.nsstlfep04p-svc.bpe.nexus.telstra.com.au@extmail.bigpond.com>
          for <myaddress@bigpond.com>; Fri, 28 Apr 2017 13:30:04 +1000
Received-SPF: fail (extmail.bigpond.com: domain mx.sailthru.com does not
 designate 72.13.32.171 as permitted sender) identity=mailfrom;
 receiver=extmail.bigpond.com; client-ip=72.13.32.171;
 envelope-from=delivery@mx.sailthru.com; helo=mx02.nic.name;
X-Junkmail-Premium-Raw: score=8/85,refid=2.7.2:2017.4.27.183916:17:8.129,ip=72.13.32.171,rules=DKIM_SIGNATURE,
 DATE_TZ_NA, __HAS_FROM, FROM_NAME_PHRASE, __TO_MALFORMED_2, __TO_NO_NAME,
 __HAS_MSGID, __SANE_MSGID, __SUBJ_ALPHA_END, __MIME_VERSION, __CT,
 __CTYPE_MULTIPART_ALT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART,
 __HAS_X_MAILER, __HAS_LIST_UNSUBSCRIBE, __MIME_TEXT_P2, __MIME_TEXT_H2,
 __ANY_URI, __URI_WITH_PATH, __URI_NO_MAILTO, __URI_NO_WWW, __CP_MEDIA_BODY,
 __CP_NAME_BODY, __CP_URI_IN_BODY, __FRAUD_INTRO, __FRAUD_LOC,
 __SUBJ_ALPHA_NEGATE, __INT_PROD_LOC, __LINES_OF_YELLING, __MULTIPLE_URI_TEXT,
 __URI_IN_BODY, __URI_NOT_IMG, __NO_HTML_TAG_RAW, BODY_SIZE_10000_PLUS,
 BODYTEXTH_SIZE_3000_MORE, __MIME_TEXT_H1, __MIME_TEXT_P1, __MIME_HTML,
 LINES_OF_YELLING_3, __URI_NS, HTML_00_01, HTML_00_10, __PHISH_SPEAR_GREETING,
 __HAS_LIST_HEADER, __LEGIT_LIST_HEADER, __FRAUD_COMMON, CHILD_EX_X3,
 __MIME_TEXT_H, __MIME_TEXT_P, NO_URI_HTTPS, URI_WITH_PATH_ONLY
Received: from mx02.nic.name (72.13.32.171) by extmail.bigpond.com (9.0.019.11-1)
        id 58DA9AA41B45BAE6 for fname@lname.name; Fri, 28 Apr 2017 13:30:04 +1000
Received: from mx-washpost-a.sailthru.com (mx-washpost-a.sailthru.com [192.64.237.165])
	by mx02.nic.name (Postfix) with ESMTP id E7FD62D02
	for <fname@lname.name>; Thu, 27 Apr 2017 20:11:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; s=mt; d=pmta.sailthru.com;
 h=Date:From:To:Message-IDubject:MIME-Version:Content-Type:List-Unsubscribe;
 bh=CZEWPPksLYl8ze3dhLQtFlsCB/8=;
 b=cmb2YRuoU/zgc+h6bMlCO31grQHQeWTRVRaS6vZ98Xwc4pnDbWrAU9Z2WDxyjQB0I7u/wL9D1dPr
   GUCM6HYf2S6OH6FHWo9aNgz05ztwrja1tceS8j+adv7xx+BIu7ALnkdmNdlqs9yNYHAFCl2Xe9rq
   JcyZcffVI3YiI/dKlok=
Received: from njmta-90.sailthru.com (173.228.155.90) by mx-washpost-a.sailthru.com id h098781qqbs9 for <fname@lname.name>; Thu, 27 Apr 2017 16:11:32 -0400 (envelope-from <delivery@mx.sailthru.com>)
Received: from nj1-newyonder.flt (172.18.20.6) by njmta-90.sailthru.com id h098781qqbs9 for <fname@lname.name>; Thu, 27 Apr 2017 16:11:31 -0400 (envelope-from <delivery@mx.sailthru.com>)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; t=1493323891;
	s=sailthru; d=e.washingtonpost.com;
	h=Date:From:To:Message-IDubject:MIME-Version:Content-Type:List-Unsubscribe;
	bh=JXmtRcrXwizUdDjy0+AJ7WKAPN3dney4E0SGzVDTRaU=;
	b=V2x0ro4Nzi3y3lbMlRfjwGDcJ7ld8wNfUyauMfZe+dH+UzTq4TOnAOoY31O/K5TP
	8AyvvmIlR+pOZR2utlY4NQRtC8Q4zpAi3mVkexsfTiInttXBxPy3DMVbEbqIDdCUeIF
	Tq5vJ3i1D3sbVS6Cxx5nbVSwaaMmJmejXSTjG5bA=
Date: Thu, 27 Apr 2017 16:11:31 -0400 (EDT)
From: The Washington Post <email@e.washingtonpost.com>
To: fname@lname.name
Message-ID: <20170427161131.9484591.140863@sailthru.com>
Subject: The Post Most: North Korea puts out new video showing the White
 House in crosshairs and carriers exploding
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_15157414_399701187.1493323891209"
Precedence: bulk
X-TM-ID: 20170427161131.9484591.140863
X-Info: Message sent by sailthru.com customer The Washington Post
X-Info: We do not permit unsolicited commercial email
X-Info: Please report abuse by forwarding complete headers to
X-Info: abuse@sailthru.com
X-Mailer: sailthru.com
X-Unsubscribe-Web: http://link.washingtonpost.com/oc/578fbf136e4adc414f8b4d295nacv.30ov/28d6af86
List-Unsubscribe: <http://link.washingtonpost.com/oc/578fbf136e4adc414f8b4d295nacv.30ov/28d6af86>, <mailto:unsubscribe_20170427161131.9484591.140863@mx.sailthru.com>
X-rpcampaign: sthiq9484591

Throwing this into the Messageheader analyser at G Suite Toolbox, you can see the 7 hour delay, once the email hits extmail.bigpond.com. 

MessageId	
20170427161131.9484591.140863@sailthru.com
Created at:	4/28/2017, 6:11:31 AM ( Delivered after 7 hours )
From:	The Washington Post <email@e.washingtonpost.com> Using sailthru.com
To:	patrick@turner.name
Subject:	The Post Most: North Korea puts out new video showing the White House in crosshairs and carriers exploding

#	Delay	From*			To*	Protocol	Time received	
0	1 sec	mx-washpost-a.sailthru.com	→		mx02.nic.name	ESMTP	4/28/2017, 6:11:32 AM	
1	7 hours	extmail.bigpond.com	→		nsstlfep04p-svc.bpe.nexus.telstra.com.au		4/28/2017, 1:30:04 PM	

My question is, is there anything Telstra and/or I can do, other than not using a bigpond email address, to rectify this? It's increasingly becoming a problem with urgent emails, validating logins, changing passwords, online shopping etc.  Also, note, I doubt my ability to get Verisign to change their server configurations, based on my ISP's requirements, although Telstra may be able to do this on my behalf.

Also, as an aside, if a message gets a Received-SPF: fail, how does it get through to me at all? Is this a manual process where someone inspects/releases my private emails?

Hope someone can assist.