E-mail password window keeps popping up

me too

Netscape 7.0 WinXP Pro
I have been having the same problem for months if you learn anything about this please let me know.

 

broni,

Just a shot in the dark, I do not have and never had the lines mentioned so I do not know where or why.


Aside from this, you may be able to "back door" this by placing the corrective entries in your user.js file not your prefs.js file.

I would first check under Edit->preferences .....Privacy-> manage passwords:

and delete any that look like they may refer to you email accounts.


Shut Down NS.

Re-start and try and access email, enter Password, Select remember,
and see what happens.

This is just my opinion, I could be wrong.

regards:

 

broni,

Did you shut down your computer for the night? After making the corrections in your prefs.js file, did you save the changes? If you forgot and then shut down the system, it would come back. That's the only thing I can think of right now.

 

Broni, I run Adelphia cable and my system does the exact same thing periodically.

It's always their problem and not mine. The first time it happened I went through the whole system looking for the answer. It wasn't to be found. It rarely lasts over a couple hours but it has happened so many times I don't pay any attention now. It always says that my password was refused and requests that I reenter it. When I do that, it asks again, over and over.

If it persists for an extended time, I'd call them and chew them out but since it's of short duration, I just accept it. Your own experience may require different action.

 

I to have experienced this same erratic pattern. I have NOT been able to eliminate it, I have been able to reduce it considerable. I kept increases my time cycle for "Check for new messages ". Not knowing WHAT was failing in the check mail cycle, just reducing request cycles has helped. From checking every 5 minutes to every 20 minutes has reduced it to one event every 200 hours on net.

 

I think we both are in agreement... just looking at it differently. The dynamics of the entire network are bound to flip a 0 into a 1 in error. All of us have received corrupted downloads, even though they were handled by error corrected transfers. We have no control over mismanaged ISP's, high data spikes, bad line or weather condtions. When your email client handshakes with your ISP, these conditions come into play. My use of reducing cycles does not correct short time problems, it is a long term strategy.
PS... Real time update.......................
This is the second time I re-type and posted this same post. I sent the first post at 11:00 pm CST. BUT BBS. data base burped when I "Submitted the message" and lost the post. (Arnie, you should be able to verify, the error screen said it would notify you). Like I said, it's just one of them things you can reduce, but difficult to eliminate.

 

broni,

You are probably exacerbating your problems with your 1 minute setting. The time frame for checking messages shouldn't be reduced to less than 5 minutes. That isn't written in stone, but has been proven to be pretty much the standard for most ISP's.

Ramona

 

Interesting

I have followed this thread with interest because it so closely matches my own experience. Let me introduce my theory. I think that it is both ISP and Netscape at fault. When Netscape encounters a problem connecting to email I believe it deletes the login information. So what happened to Broni would be explained. Broni entered the new password everything worked fine==near the end of her online session Netscape checked email failed and deleted her login info==Broni shut down==next morning by magic login info is gone. Can anyone think of a way to test this theory? If it is true can we make Netscape retain the login info?

 

Hi iamnotanumber

I agree totally. It's program interaction between email client software / ISP software held hostage by the dynamics of maintaing a perfect communication bridge. I assume Netscape could create a more forgiving handshake, better code to manage mail downloads. But for whose ISP running which server software under what conditions managed by how well of a trained staff providing access to how many users demanding what level's of service (shisss, say that it one breath). Moving targets can be hit, it's just expensive. I feel as "the WEB" matures... User's will be able to buy/pay for a variety of service level's. The one overall constant... Netscape, ISP's and user's all have a budget.

 

Dead End?

Netscape must time out waiting for some email reply from the ISP. Unless we can tweak those settings I don't see a solution to this problem. Noone who has this level of knowledge seems to listening to our pleas.