-
Now it is Bigpond’s turn to block digest emails
Part of the never ending challenge of keeping TgR running.
Now it is BigPond’s turn to reject the digest messages as spam.
So if you have a bigpond email address you won’t be hearing from us until the email block is cleared.
This seems to happen in a week or so.,For the tech savey among us here is the bounce message I’m getting in bulk each time the digest goes out.
Quote:Reporting-MTA: dns; server-1t-r17.ipv4.per01.ds.network
Received-from-MTA: smtp; cp-qh01.syd02.ds.network (122.201.124.42)
Original-Envelope-Id: 686ed665-9248-11ea-96c1-f8db88ea9a09
Arrival-Date: Sat, 09 May 2020 22:57:07 +0000Final-Recipient: rfc822; youremaili@bigpond.com
Action: failed
Status: 5.7.1 (5E83E6340AF552A6 Message content rejected due to suspected spam. IB703)
Remote-MTA: dns; bigpond.com
Diagnostic-Code: smtp; 558 5.7.1 5E83E6340AF552A6 Message content rejected due to suspected spam. IB703 -
4 Replies
-
I’m one of the geeky techy types (soz!). Would creating a SPF txt record in DNS help? tgr.net.au doesn’t seem to have one and could help with SPAM Assassin SPF module (or most other filters) to apply a more favourable score when calculating. At a guess, v=spf1 mx include:tgr.net.au -all or something similar (depending on how the mail flow is configured) would be it.
-
Vanessa was right….
The website move resulted in the email security stuff being a mess. I couldn’t fix it, and the support person needed special God powers to restore things. But all should now be well! -
My advice is to drink heavily. I should point out that it is my advice for everything.
-
Sage advice, my friend, sage advice …
