No e-mail on legacy callnetuk.com account

[#1]

I've seen a couple of similar posts in the forums these last couple of days.

Mine is callnetuk.com and whilst I'm not getting any error messages and can log onto webmail, I'm not actually seeing any new mail.

Thanks.

[#2]

Is the mailbox full?

[#3]

Thanks for the reply. 

Definitely not. It's POP3, not IMAP, so there's usually not very much at all sat on the server as I pick it up multiple times a day.

I have received the occasional email today, but I'd normally get 100+ by lunchtime.

[#4]

I have the same issue - I'm not seeing any new mail from my callnetuk.com address. I have been in contact with the help desk but they dont know what the problem is as there is no error message other than 'Unable to connect to the incoming server'.

I can log into my webmail. I can see mail up to Sunday night (1 Oct). I can send email through the webmail portal.

The mailbox is POP3 and is only 22mb. Incoming server is mail.callnetuk.com

[#5]

We did not get any emails since last night either on our callnetuk accounts (we have two). There is no connection to the email servers on POP3 or IMAP. When using the webmail access, I can log into the accounts but the new email foder is empty (no new emaisl since yesterday evening).

Checking the error, I found out that the domain "callnetuk.com" expired on 1st October and the update was fed into the DNS system yesterday (see whois screenshot).

It appears to be that this is the reason why no emails are received to the server and no access through the domain.

As the domain is set to auto-renewal, the "normal" reason for non-renewal is non-payment of the registrar's fees 🙂

Really? This bill should be well below £20 per year.

Is anyone at Plusnet working on this?

[#6]

Prompted by the email problems with the legacy callnetuk.com email accounts, I stumbled over the situation with this domain.

It appears that plusnet have let the renewal of the domain lapse, causing all internet traffic to the domain "callnetuk.com" to fail. Hence no email sending or receiving possible any more.

I hope someone at plusnet is paying this $10 bill reight now to solve this problem

The whois entry for the domain:

Whois Record for CallNetUk.

Registrar Status	autoRenewPeriod, clientTransferProhibited
Dates	9,132 days old Created on 1998-10-02 Expires on 2023-10-01 Updated on 2023-10-02

[#7]

Nice one, JamesRK. That explains why senders are receiving:

0 5.4.316 Message expired, connection refused. Socket error code 10061. Last attempted server name: callnetuk.com. Last attempted IP: 15.197.172.60:25

[#8]

Moderator's note(s):

Threads merged to keep support in one place.

[#9]

Ticket raised with Plusnet.

Extract from an email with the support desk:

Our Support Team have opened Ticket 237343222 to track an issue on your account. Please see the comments shown below for more information.

==============

Hello

Thank you for your time on the phone, your issue with receiving emails has now been escalated and we await the teams response, this has a time of 72 hours, thank you again for the authorization to change your password for testing.

REF:INFOPS-97734

==============

I have also sent them the Callnet DNS.png file that is attached to JamesRK post.

According to their email, I should get an answer within 72 hours.

[#10]

72 hours... I'd be facing a disciplinary if it took me 72 minutes to renew a domain name...

[#11]

Good detective work - I have escalated the matter.

[#12]

Thanks Townman.

[#13]

I It too have the same issue on both my callnetuk accounts, except that daily e-mails from one particular sender *are* still getting through to me, as of yesterday anyway. Strange, given another poster's discovery that the callnetuk.com domain name has not been renewed.

[#14]

Sorry, I withdraw the above posting. The e-mails to which I refer were forwarded to my local (Thunderbird) callnetuk inbox from another account. I haven't received anything from callnetuk since 25th September.

[#15]

The relevant teams are aware of this issue and I expect DNS will spring back to life over the next 24hrs or so.
Thanks for flagging, and apologies for the misstep.