This issue is nearly 24 hours old. I was happily sending emails before dinner last night, went on to do some more and I can't send anything due to Error Code 553.
I have tried sending myself a test message with just the heading, but that does not work ie it won't permit me to send.
Emails are still coming in, but I can't respond to them.
I tried logging on the BT email via other servers ie Google, Edge, Yahoo and whilst I can do this the same rules apply try to send an email Error Code 553.
I turned off the Home Hub for an hour, this made no difference to the problem.
Your help to resolving this hugely frustrating issue would be appreciated, but may I ask one favour please? On this sort of thing I am an utter technophobe, please if you are going to offer up a technical explanation, the simplest version would be most welcome, thanks so much.
I would add that I go into my BT email home page via Chrome and then log via the BT email log in.
I hope this is enough to be going on with and we resolve this very soon. Again, sincere thanks in advance.
Solved! Go to Solution.
On my Kindle I am able to send myself a test email, no text. I then forward it back to my account, it works.
The same applies in using my Lenovo Tablet.
However, it remains impossible to send emails on either my own or my work laptop without 533 error message.
I really would be grateful for your thoughts. Thanks.
Hi, @Oxymoron I'm sorry you're getting the 553 error when sending emails. Are you using a VPN on the laptops, if so can you disable it and try to send an email?
@Oxymoron as the error is only happening on your laptops and not on the tablets it points to something on the laptops causing the error.
I'm not familiar with ESET, however, I did notice they provide something called endpoint encryption when I googled it, which might be the reason behind the error. Are you able to deactivate that for testing purposes?
Thanks for posting back.
I am sorry for the error 553 when sending emails from your laptops. I have sent you a private message with instructions on how you can send us over your details and we'll see if we can get to the bottom of why you're seeing this error code. See: Private messages