If I send an email to an address on bigpond.com (Australia) I get the following returned some 4-5hrs later. It all points to a problem with bigpond. But I have no problems sending to that address with either gmail or using my works email system. It only happens using idnet.com, both from webmail and pop. Anyone with any ideas? Could idnet be being blacklisted by bigpond?
=======================================
This is the mail system at host smtp.idnet.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<xxxxxx@bigpond.com>: lost connection with extmail.bigpond.com[61.9.168.122]
while sending end of data -- message may be sent more than once
Reporting-MTA: dns; smtp.idnet.com
X-Postfix-Queue-ID: C2A69634B3
X-Postfix-Sender: rfc822; me@idnet.com
Arrival-Date: Mon, 28 Apr 2014 19:04:13 +0100 (BST)
Final-Recipient: rfc822; xxxxxx@bigpond.com
Original-Recipient: rfc822;xxxxxx@bigpond.com
Action: failed
Status: 4.4.2
Diagnostic-Code: X-Postfix; lost connection with
extmail.bigpond.com[61.9.168.122] while sending end of data -- message may
be sent more than once
To be honest, I think you'd be better off forwarding that bounce message to IDNet themselves, as we'd only be guessing here.
It's possible that bigpond have blocked IDNet emails, but I'd guess that's unlikely, and the message seems to point more towards a DNS / connection issue.
OK. Have sent a copy to support. Will see what they say.
Thanks.
Just to update this.
I sent the details to both bigpond and idnet support. No reply from idnet, but bigpond did reply, although not very helpfully.
Now after three days of not working, all is suddenly well again. Obviously something was "broke", but who knows? ???
The magical fixit fairy strikes again! It would have been nice to have known the reason for the failure, but at least it's working now.