Creating 2nd Acct on NNTP server causes both accts to fail



Account Manager
13 years ago
13 years ago


(Reporter: Donald D Henson, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 SUSE/1.0.3-1.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 SUSE/1.0.3-1.1

I inadvertently attempted to create a second account on an NNTP server. The
server uses SSL and requires authentication. After apparently creating the
second account, I was unable to logon to the NNTP server using what I thought
was the new account. After realizing what I had done, I deleted the account that
was showing and restarted Thunderbird. It appeared that the account had not been
deleted but I think that was, instead, a second account on that server. I
deleted the account again and again restarted Thunderbird. The account was now
gone and I was able to recreate the account from scratch.

Reproducible: Always

Steps to Reproduce:
1. Create an NNTP account on a server that uses SSL and requires authentication.
2. Attempt to create a second account on that same NNTP server.
3. Try to subscribe to a newsgroup on that NNTP server.

Actual Results:  
The account manager (?) attempted to log on but eventually timed out.

Expected Results:  
I would have expected the account manager (?) to issue a warning that you should
not attempt to create a second account on a given server and then back out of
the creation of the second account, leaving the original account intact.

The NNTP server I was using when the difficulty occurred is one maintained by
the University of Phoenix Online University. It's possible that they may have
modified the software but I don't think that's the problem here.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.