suddenly my gmail account inside WLM (windows live mail)wont connect to server, and will not send out emails anymore.
the first error:"cannot connect to IMAP server xxx.xxx.x.x:143 (my routers IP address), error 10061…configuration IMAP…Port 143…code 800ccc0f…etc)
after rebuilding the account, i got error: “An unknown error has occurred.Subject ‘weeee’. Server Error: 421.Server Response: 421 Cannot connect to SMTP server 74.125.157.109 (74.125.157.109:25), connect error 10060. Server: ‘smtp.gmail.com’.Windows Live Mail Error ID: 0x800CCC67. Protocol: SMTP. Port: 25. Secure(SSL): No.”
+other errors also…
problem is ONLY from the wireless laptop. i have a 2wire Gateway 2701 modem/router wired to a desktop. on the desktop all works perfectly. all email, firewall, avast, settings were identical on both machines. originally avast, smtp #465, imap #993. WLM, smtp #25, imap #143.
the only combination to get it to work now is avast, smtp #465, imap #993. In WLM, smtp #587, imap #143.
why did i have to change to smtp #587 in WLM all of a sudden?
I’m wondering, is the mail shield in Avast started/on?
Windows live mail would not be able to connect to gmail server with an insecure connection on both imap and smtp. If the mail shield was off this connection would be through WLM which is insecure ports 25 and 143. Since you changed it to an SSL port it is now connecting.
That would be very strange if that were the case. I don’t see why the desktop hibernating would cause problems with the laptop.
When you say “rebuilding the account”, do you mean in Windows Live Mail? Did you delete the SSL accounts in Avast and let Avast find the SSL connections again?
Maybe resetting the router may help and/or rebooting the laptop. Some sort of connectivity problem? Please let me know what you find out as I am curious to know. I have a laptop and desktop connected wireless to a router and don’t have either one set to hibernate.
I believe those are the IP addresses for the mail server. I have had it happen too. I have always wondered if the gmail server was busy and was redirected to a different one. Don’t know for sure.