Closed
Bug 57834
Opened 25 years ago
Closed 25 years ago
Replying to netscape.public.mozilla.general does not work.
Categories
(MailNews Core :: Networking: NNTP, defect, P3)
Tracking
(Not tracked)
People
(Reporter: fuerte, Assigned: sspitzer)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; m18) Gecko/20001024
BuildID: Gecko/20001024
Replying to netscape.public.mozilla.general does not work. Other newsgroups in
the same server work ok. I get an error:
"NEWS ERROR: An authorization error occurred. Please try entering your name
and/or password again. Could not get your access name. Goodbye."
Posting new messages works ok.
Reproducible: Always
Steps to Reproduce:
Actual Results:
Expected Results:
|
Reporter | |
Comment 1•25 years ago
|
||
I now know at least something what is going on. I have two ISPs, Saunalahti and
NIC. When using Saunalahti, replying to newsgroups works ok always. When using
NIC, replying to newsgroups does not usually work, except to this newsgroup, for
example. Still posting new messages works always.
This does not make much sense, except that I have two mail accounts, one for
fuerte@sci.fi (Saunalahti) and the other for fuerte@nic.fi (NIC). My outgoing
SMTP server is smtp.nic.fi. Still I always use the e-mail address fuerte@sci.fi
when posting messages. It seems that when I reply to newsgroup, Mozilla contacts
the mail server for some reason (smtp.nic.fi?) and checks if the fuerte@sci.fi
is a valid e-mail address. Could it be?
This does not make any sense... especially when posting new messages works always.
I tried changing the e-mail address to fuerte@nic.fi, but it didn't help. But
definitely it has something to do with the mail servers, because when I use
Saunalahti, replying to newsgroups works.
Now somebody developing Mozilla should check if Mozilla is contacting *e-mail*
server (outgoing or incoming) when posting to newsgroups. It would explain the
error message:
"NEWS ERROR: An authorization error occurred. Please try entering your name
and/or password again. Could not get your access name. Goodbye."
|
|
Reporter | |
Comment 2•25 years ago
|
||
I used TDIMon (http://www.sysinternals.com/) to resolve this bug. I noticed than
when I post a new message to netscape.public.mozilla.general, then it contacts
only secnews.netscape.com (198.95.249.40). But when I reply to a message, then
it contacts news.sci.fi (195.197.54.114). This must be a bug.
I have attached the TDIMon logs. The first one is the post, the second one is
the reply.
1
0.00000000
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-5
Length:1
2
0.00011120
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
3
0.01236000
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-6
Length:1
4
0.01246640
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
7
0.01846560
Mozilla
E1AFBFB0
TDI_OPEN_ADDRESS
TCP:0.0.0.0:1098
SUCCESS
8
0.01848080
Mozilla
E1AFBFB0
TDI_QUERY_INFORMATION
TCP:0.0.0.0:1098
SUCCESS Query Address
9
0.01849280
Mozilla
E1AFBFB0
TDI_SET_EVENT
TCP:0.0.0.0:1098
SUCCESS Disconnect Event
10
0.01850320
Mozilla
E1AFBFB0
TDI_SET_EVENT
TCP:0.0.0.0:1098
SUCCESS Receive Event
11
0.01851360
Mozilla
E1AFBFB0
TDI_SET_EVENT
TCP:0.0.0.0:1098
SUCCESS Expedited Receive Event
12
0.01852480
Mozilla
E1AFBFB0
TDI_SET_EVENT
TCP:0.0.0.0:1098
SUCCESS Datagram Receive Event
13
0.01855920
Mozilla
8A000061
TDI_OPEN_CONNECTION
Connection obj SUCCESS
14
0.01857440
Mozilla
8A000061
TDI_ASSOCIATE_ADDRESS
Connection obj SUCCESS TCP:0.0.0.0:1098
15
0.01859680
Mozilla
8A000061
TDI_CONNECT
TCP:0.0.0.0:1098
198.95.249.40:119
SUCCESS
16
0.21860880
Mozilla
8A000061
TDI_QUERY_INFORMATION
TCP:0.0.0.0:1098
198.95.249.40:119
SUCCESS
Query Address
17
1.40627440
Mozilla
E1AFBFB0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1098
198.95.249.40:119
MORE_PROCESSING
Length:80 Flags: ENTIRE_MESSAGE LOOKAHEAD
18
1.40730480
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-21
Length:1
19
1.40739520
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
20
1.40816320
Mozilla
8A000061
TDI_SEND
TCP:0.0.0.0:1098
198.95.249.40:119
SUCCESS-23
Length:6
22
1.60578240
Mozilla
E1AFBFB0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1098
198.95.249.40:119
MORE_PROCESSING
Length:8 Flags: ENTIRE_MESSAGE LOOKAHEAD
24
1.60884880
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-27
Length:1
25
1.60894160
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
26
1.61009680
Mozilla
8A000061
TDI_SEND
TCP:0.0.0.0:1098
198.95.249.40:119
SUCCESS-28
Length:519
29
3.22751280
Mozilla
E1AFBFB0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1098
198.95.249.40:119
MORE_PROCESSING
Length:20 Flags: ENTIRE_MESSAGE LOOKAHEAD
1
0.00000000
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-4
Length:1
2
0.00011280
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
3
0.03195920
Mozilla
4B00002C
TDI_SEND
TCP:0.0.0.0:1055
198.95.249.40:119
SUCCESS-6
Length:39
5
0.23940400
Mozilla
E193D4E0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1055
198.95.249.40:119
MORE_PROCESSING
Length:51 Flags: ENTIRE_MESSAGE LOOKAHEAD
7
0.24037280
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-10
Length:1
8
0.24045520
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
9
0.24120880
Mozilla
4B00002C
TDI_SEND
TCP:0.0.0.0:1055
198.95.249.40:119
SUCCESS-12
Length:15
11
0.44407600
Mozilla
E193D4E0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1055
198.95.249.40:119
MORE_PROCESSING
Length:32 Flags: ENTIRE_MESSAGE LOOKAHEAD
13
0.46862800
Mozilla
E193D4E0
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1055
198.95.249.40:119
MORE_PROCESSING
Length:160 Flags: LOOKAHEAD
14
13.00573360
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-18
Length:1
15
13.00584720
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
16
13.04514800
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-19
Length:1
17
13.04525280
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
20
13.04672480
Mozilla
E205A950
TDI_OPEN_ADDRESS
TCP:0.0.0.0:1099
SUCCESS
21
13.04674000
Mozilla
E205A950
TDI_QUERY_INFORMATION
TCP:0.0.0.0:1099
SUCCESS Query Address
22
13.04675200
Mozilla
E205A950
TDI_SET_EVENT
TCP:0.0.0.0:1099
SUCCESS Disconnect Event
23
13.04676160
Mozilla
E205A950
TDI_SET_EVENT
TCP:0.0.0.0:1099
SUCCESS Receive Event
24
13.04677280
Mozilla
E205A950
TDI_SET_EVENT
TCP:0.0.0.0:1099
SUCCESS Expedited Receive Event
25
13.04678320
Mozilla
E205A950
TDI_SET_EVENT
TCP:0.0.0.0:1099
SUCCESS Datagram Receive Event
26
13.04681600
Mozilla
8B000062
TDI_OPEN_CONNECTION
Connection obj SUCCESS
27
13.04683040
Mozilla
8B000062
TDI_ASSOCIATE_ADDRESS
Connection obj SUCCESS TCP:0.0.0.0:1099
28
13.04685280
Mozilla
8B000062
TDI_CONNECT
TCP:0.0.0.0:1099
195.197.54.114:119
SUCCESS
29
13.07611840
Mozilla
8B000062
TDI_QUERY_INFORMATION
TCP:0.0.0.0:1099
195.197.54.114:119
SUCCESS
Query Address
30
13.23431280
Mozilla
E205A950
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1099
195.197.54.114:119
MORE_PROCESSING
Length:47 Flags: ENTIRE_MESSAGE LOOKAHEAD
31
13.23965200
Mozilla
E205A950
TDI_EVENT_DISCONNECT
TCP:0.0.0.0:1099
195.197.54.114:119
SUCCESS
RELEASE
32
14.88157520
Mozilla
26000025
TDI_SEND
TCP:127.0.0.1:1027
127.0.0.1:1028
SUCCESS-37
Length:1
33
14.88167920
Mozilla
E1BD5760
TDI_EVENT_RECEIVE_EXPEDITED
TCP:0.0.0.0:1028
127.0.0.1:1027
MORE_PROCESSING
Length:1 Flags: ENTIRE_MESSAGE LOOKAHEAD
34
14.89434560
Mozilla
8B000062
TDI_DISCONNECT
TCP:0.0.0.0:1099
SUCCESS
35
14.92049520
Mozilla
8B000062
TDI_CLOSE_CONNECTION
TCP:0.0.0.0:1099
SUCCESS
36
14.92053600
Mozilla
E205A950
TDI_CLOSE_ADDRESS
TCP:0.0.0.0:1099
SUCCESS
|
|
Reporter | |
Comment 3•25 years ago
|
||
Still I can't understand why replying to netscape.public.mozilla.mail-news works OK.
|
||
Comment 4•25 years ago
|
||
Harri, do you still see this issue?
Moving to Networking - News...
Assignee: putterman → sspitzer
Component: Mail Window Front End → Networking - News
Hardware: Other → PC
|
|
Reporter | |
Comment 5•25 years ago
|
||
It started working after I removed news.sci.fi account (a couple of weeks ago).
|
|
||
Comment 6•25 years ago
|
||
Resolving WORKSFORME based on previous comment by the reporter...
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
|
|
Reporter | |
Comment 7•25 years ago
|
||
But if nothing was done, then the bug is still there: Replying to newsgroups
sends the message to incorrect server, if it finds the newsgroup name from a
different account.
|
|
||
Comment 8•25 years ago
|
||
OK, I'll reopen and mark a dependency on bug 54911 as I believe (and based on
the last comment in that bug, so do you) that they are related...
|
|
||
Updated•25 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Mass moving all NEWS bugs from esther to myself.
QA Contact: esther → stephend
I read over 54911, and it seems that it covers this bug entirely, especially
since it also mentions multiple servers, and the problem you encounter with
regards to having messages sent to the wrong server. Anyone agree?
*** This bug has been marked as a duplicate of 54911 ***
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
|
||
Updated•21 years ago
|
Product: MailNews → Core
|
||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•