email ver 2.18.2

[dazbon]

And now what? Been putting up with it by giving up and using gmail to send simple emails as since the latest update at what appears to be random events, it now decides that there is either a problem with url, possible spam or malware within the email. Pops up with error message & refuses to send just a simple email with nothing suspicious etc within it.

What the hell, with each "improvement" my email seems to be getting worse. 

All I can say is that Microsoft has carried out another autoupdate with windows 10 around the same time & so not sure if it is a possible compatibility / security setting issue?

[Stephen5000]

---

@dazbonwrote:

And now what? Been putting up with it by giving up and using gmail to send simple emails as since the latest update at what appears to be random events, it now decides that there is either a problem with url, possible spam or malware within the email. Pops up with error message & refuses to send just a simple email with nothing suspicious etc within it.

What the hell, with each "improvement" my email seems to be getting worse. 

All I can say is that Microsoft has carried out another autoupdate with windows 10 around the same time & so not sure if it is a possible compatibility / security setting issue?

---

I have been on v2.19.0 for a couple of weeks now and it seems to be very stable. Couple of features still not working, but have been promised in v2.20.0. Hopefully if you are still on v2.18.2, you'll be updated soon and the issues you are experiencing will subside...

[dazbon]

Thanks Bud, hope so as real pain copy/paste & then open Gmail just to get it sent.

[dazbon]

Yep still coming up with error code 553 & can't understand why, have looked through all my settings etc but just not seeing why this is happening on a standard email I am trying to send to a solicitor?

[Stephen5000]

---

@dazbonwrote:

Yep still coming up with error code 553 & can't understand why, have looked through all my settings etc but just not seeing why this is happening on a standard email I am trying to send to a solicitor?

---

There are several threads that now that mention the 553 error specifically - not sure if they'll be any help...

https://community.bt.com/t5/Email/Error-Code-553/td-p/2096561

https://community.bt.com/t5/Email/ERROR-CODE-553/td-p/2068624

https://community.bt.com/t5/Email/Error-Code-553/td-p/2058127

[dazbon]

From reading the post suggested it appears that BT suggestion is to turn off VPN & then it might work. This can not be right in my opinion & is something that needs sorting out from their end surely?

No problem with this until the update to 2.18.2, which is the ver that I am still on.

A few comments suggested that after letting BT know about this the issue appeared to rectify itself a day or so later, but does look like BT are not admitting directly to the issue.

A standard email to a legitimate solicitor with no suspicious content should send without issue, as it does in Gmail! 

[JohnC2]

Hi @dazbon, would you retry outside your VPN and see if that solves the problem. 

cheers

John

[dazbon]

Was fine before update so not sure turning off VPN is the answer but will give it a go. Hopefully when I get the nxt update things will improve and emails will send without flagging up an error.

[dazbon]

As it was saved in drafts thought I would give it one more go & see if it would send. Sent with no error & still not sure why it would not work the other 6 times (three of them being attempts from Drafts), so closer to understanding why, as it sent with the VPN enabled?

[Stephen5000]

Apparently v2.19.0 is returning to us W/C 23rd November, though I still have no idea why it was withdrawn in the first place!