More Gmail Sending & Receiving Woes

by on February 7, 2006

in Email

Gmail’s been pretty sluggish for me today. Then about a half-hour ago, I lost the ability to send email through it. I tried the usual step of deleting my account in Outlook and reestablishing it, as I covered here. No luck. I still can’t send. I suspect the problem is linked to the new chat feature that Google’s rolled out within Gmail.

Google has a bad habit of rolling out new products that get quickly overwhelmed by demand. Web Accelerator and Google Analytics are examples of this. Now Gmail appears to be another victim, and I hope they fix it soon.

So far, I’ve been treated to these error messages:

  • Error (0x800CC78). Unable to send the message. Please verify the e-mail address in your account properties. The server responded: 530 5.7.0 Authentication Required k24….
  • Error (0x800CCC92). Your e-mail server rejected your login. Verify your user name and password in your acount properties. Under Tools, click E-mail accounts. The server responded: -ERR [SYS/TEMP] Proxying required, but not implemented.
  • The server responded: 42 4.7.0 Temporary System Problem. Try again later. g1s…

That first message came up despite the fact that Outlook was able to send a test message just fine.

The second message comes along with Gmail occasionally demand my password again through Outlook even though it is definitely entered correctly and works on other occasions. I did a quick search, and this type of thing has happened before.

For the moment, I’m having to send through a secondary email account. As for receiving, hopefully that will clear up soon.

Postscript: Google tells me they’ve had no reported problems. I deleted my Gmail settings from Outlook a third time, and now things are working again.

Share

{ 2 comments }

1 liam morrison February 7, 2006 at 3:21 pm

I had the same problem this morning. For a while around 10.30, gmail could not send email.

2 Ludwixx January 15, 2011 at 2:09 pm

same problem!

Comments on this entry are closed.

Previous post:

Next post: