On 24/11/11 15:56, David E. Ross wrote:
> On 11/24/11 1:51 AM, Torsten Villnow wrote:
>> Am 24.11.2011 05:28, schrieb Beauregard T. Shagnasty:
>>> Cy Burnot wrote:
>>>
>>>> Beauregard T. Shagnasty has written on 11/23/2011 9:26 PM:
>>>>> Cy Burnot wrote:
>>>>
>>>> <snip>
>>>>
>>>>>>> It's not the news group, it's the news server, actually.
>>>>>>
>>>>>> This happens a lot with eternal-september.
>>>>>
>>>>> I'd suspect something else as I have been using E-S for years and do
>>>>> not see any username/password problem. But then I don't use Thunderbird
>>>>> for News. (I don't use Windows either.<g>)
>>>>
>>>> This is a Thunderbird support group. Just how is your message
>>>> supportive?
>>>
>>> You seem to want to blame Eternal-September for the problem. I stated
>>> that I've never had those kinds of problems. How is that not supportive?
>>
>> I have the same problem with another news server -
news.individual.de
>> (see my post below). These problems had never occurred with TB 1 to 7,
>> they only recently started with TB 8 and are gone again now after having
>> reinstalling TB 7. Therefore I also have to "blame" TB 8 for causing
>> this problem. So your post is IMHO supportive.
>>
>> --
>> Torsten Villnow
>
> I first saw this problem with TBird 3.1.7. It is NOT new with TBird 8.0.
>
> As I stated elsewhere in this thread, the problem is within TBird. It
> occurs when there is a problem logging-on to the NNTP (newsgroup)
> server. If the logon fails, TBird deletes the logon user ID and
> password. See<
https://bugzilla.mozilla.org/show_bug.cgi?id=437930>.
>
> Of course, the problem is indeed triggered by a problem in the NNTP
> server. I had the problem repeatedly when the Giganews server (the
> public part, not the
news.mozilla.org part) would fail to authenticate
> my logon. However, such a failure should not cause TBird to delete a
> user ID and password.
>
TB still refusing to connect to
news.individual.net whilst other
newsreaders are having no trouble. However, I agree with you that there
must be some problem with the server that is triggering this. The main
problem, though, is that TB has such flaky system that it can't cope as
well as other readers.
I've had troubles with the newsreader since it was in Netscape 1.2N and
it hasn't changed much since - apart from x-posting checks being broken
last century. At least it means that when groups get irretrievably
corrupted I can use the same tactics that worked fifteen years ago.
Unfortunately, I don't know anything works with this expletive-deleted bug.