skip to content

Latest News

Optusnet maili delivery issues

Our recent upgrade to Debian 12 (bookworm) included a tightening of security around TLS connections used for logging in and...

Server upgrades - Debian 12

This month we are busy upgrading our servers to the new Debian 12 ("bookworm"), which includes PHP 8.2 and PostgreSQL 15.3...

25 years of Chirp!

This week marks 25 years since Chirp first opened for business back in 1997 as Chirp Web Design in a small office in Braddon,...

News RSS Feed

more news

iiNet blocking relayed emails

7 December 2020

If you have an email alias/relay set up at Chirp and a mailbox hosted by iiNet you may have noticed in recent weeks that some or all of your emails are not getting through.

The issue appears to be that iiNet are relying on the (broken by design) SPF protocol which says that emails are only allowed to be sent directly from pre-authorised mail servers.

In the case of an email relay, this is not the case:

  • an email is sent to you(at);
  • it arrives at our mail server (mail.; and
  • is forwarded (relayed) to your mailbox;

If the mail server handling your mailbox is poorly configured, it thinks that is responsible for sending the original email without authorisation (i.e. spoofing) so the email is rejected:

----- Transcript of session follows -----
... while talking to
<<< 554 Your access to this mail system from XXX.XXX.XXX.XX has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
554 5.0.0 Service unavailable

The simplest solution would be for iiNet to implement a white-list, but in all probability they won't, because even while broken, SPF still allows ISPs to block a lot of spam emails.

Your other options include:

auDA rule changes »

« Sectigo Root Certificate expiry

< news archive