284017 - I am unable to download email from 1 of 2 accounts.

Status: RESOLVED EXPIRED

(Thunderbird :: Account Manager, defect)

Description

[K.A. Long]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

I have disabled my antivirus software and firewall.  I have toggled the SSL
settings and removed the saved passwords from the PW manager.  Nothing seems to
work.  My verizon.net email works fine.  My olotp.org email fails to download.
I can send and recieve email from verizon.net.  When I send email TO
[e-mail], I cannot download it.  I am able to login to the DNS provider
web site and view all my test emails via a web GUI.  I have checked the password
and it is correct.  I use the same password at the web site as in the dialog pop up.

If SSL is enabled, I only get the dialog 'connecting to server' and the response
is 'server timed out'.  

Reproducible: Always

Steps to Reproduce:
1.  Select [e-mail] from the 'Get Mail' pulldown menu.
2.  See dialog 'Host contacted.  Sending login information'.
3.  Pop up prompts me for a password and I enter it.
4.  Sending of password did not succeed.  Mail server mail.olotp.org responded:
 Invalid Login.


Actual Results:  
Mail failed to download.

Expected Results:  
Mail should have downloaded.

I have an Ethereal trace that shows the failures using no SSl and SSL.  It has
my password in clear text so I'd like to have some sort of PK cert from the
person who emails me.  Contact me at [e-mail].  That's a zero in my
account name.

Comment 1

[Daniel Veditz [:dveditz]]

If you're seeing your password in cleartext and it is what you intended to type,
and the server is responding "invalid login" maybe the server is telling the
truth? Have you tried another e-mail program, or contacted your provider?

What version of Thunderbird is this being reported against?

Since it's only happening on one provider it is probably more fruitful to work
out what the problem is interactively through one of the user groups at
http://www.mozilla.org/support/#community.  As-is I don't see how Scott could
fix this based on this bug report, and he's got enough other bugs to work on to
spend time tracking this down without more details.

Another option is to capture a log as described at
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop

I believe those logs will not reveal your password, but will point out internal
error states that a packet capture would not. You should of course double-check
that the password isn't in the log before attaching it here, I'm not 100% certain.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.