Closed Bug 340114 Opened 20 years ago Closed 17 years ago

"Failed to connect to server" after configuring to gmail with the details provided in gmail settings

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rakeshrrr, Assigned: mscott)

Details

(Whiteboard: closeme 2008-08-28)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: Mozilla Thunderbird 1.5.0.4(20060516) "Failed to connect to server" after configuring to gmail with the details provided in gmail settings. The settings are provided here: http://mail.google.com/support/bin/answer.py?answer=38343 Reproducible: Always Steps to Reproduce: 1. Configure mail accounts as given in http://mail.google.com/support/bin/answer.py?answer=38343 2. Open Thunderbird 3. There u go.. u see the error. It should have downloaded all the mails from gmail.
Same problem as reporter. I have set the account details as recommended by Gmail for Thunderbird (from help page), and checked them. I use Norton System Works/antivirus and the most current freeware version of ZoneAlarm. I am behind a linksys BEFSR41 V3 router which works with fine all applications (including Outlook). No ports are set for triggering or forwarding. Linksys has no thunderbird or gmail tech support files that I could find.
My gmail account worked fine until some time ago, but now this presenting the reported problem.
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-08-28
I no more use Thunderbird as my e-mail client.
RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.