Closed
Bug 35678
Opened 25 years ago
Closed 24 years ago
New Msg to selected newsgroup may be posted to another server.
Categories
(MailNews Core :: Backend, defect, P2)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M17
People
(Reporter: laurel, Assigned: Bienvenu)
Details
(Whiteboard: [nsbeta2+])
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Using 2000-04-12 m15 commercial build
I'm seeing postings to netscape.test wind up in another server's netscape.test
when posting via selecting newsgroup then using New Msg. I understand we may
get into a conflict situation if there are multiple subscribed groups of the
same name across different servers and we type the group name in a new compose
window when newsgroup is not selected, but I thought in 4.x we would actually
construct a url based on the group selected.
In the scenario I found, I'd subscribed to netscape.test on secnews(secure) and
also on news.mozilla.org. When I selected netscape.test on news.mozilla.org
then used New Msg, it wound up posting to secnews (on a different port?).
Note to QA, there are potentially several scenarios to test when verifying. I've
not tried those yet, but am listing only the scenario I just witnessed:
1. Migrated a 4.x profile which had several subscribed news servers including
secnews (secure, port 563) and news.mozilla.org. Both of these servers had
subscribed group netscape.test before migration.
2. Migrated the profile, opened seamonkey mail window, logged into mail
account, then opened news.mozilla.org/netscape.test newsgroup.
3. While news.mozilla.org/netscape.test group was selected in folder pane, I
clicked New Message to bring up a new message compose window, which displayed
having the Newsgroup: header filled in with netscape.test.
I composed and posted the message.
4. I got new messages in news.mozilla.org/netscape.test and did not see my
message arrive.
5. I opened the netscape.test on secnews(secure) and saw the message was posted
there.
Note: secnews (not secure, port 119) does have a netscape.test which is
listed with different number of messages and different messages (content), but
the posting turned up on secure secnews server. Wow.
Actual result: Although I initiated a new news message from a selected
newsgroup it went to another server's group by same name.
Expected Result: Message should be explicity addressed to the selected news
server when using New Msg from selected newsgroup. It should not scan the list
of subscribed groups for a match.
Comment 1•25 years ago
|
||
I need to look at how 4.x worked.
I need to find out:
1) if you posted to a group, did it use folder selection to determine the host.
2) did it try the default news server first
this bug will probably depend on me finishing up hostinfo.dat support, like most
news bugs.
accepting. apologizing.
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: --- → M16
Comment 3•25 years ago
|
||
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Comment 5•25 years ago
|
||
Comment 6•25 years ago
|
||
crap, ignore that last attachment. wrong bug.
Assignee | ||
Comment 7•24 years ago
|
||
yes, I'm pretty sure we used the folder selection to determine the news server
to post to. Phil might remember how this logic worked, since he put quite a bit
of effort into it.
Assignee | ||
Comment 8•24 years ago
|
||
taking from Seth.
Assignee: sspitzer → bienvenu
Status: ASSIGNED → NEW
Comment 10•24 years ago
|
||
The old algorithm goes like this, according to my feeble memory:
1. When the user clicks on New/Reply, we try to pick up the host based on
selection in the folder pane, and stuff that host into the compose fields for
the compose window.
2. (new in 4.5) When the user clicks Send in the compose window, if there isn't
a host, we scan the list of subscribed groups
3. (new in 4.5) If the group is subscribed on a host, we push that host into the
compose fields. If the group is subscribed on more than one host, we pick up the
first host.
4. If we still don't have a host, we use the default news host.
Assignee | ||
Comment 11•24 years ago
|
||
This is going to take some time, since I'm not familiar with the 4.5 compose
code, or the 6.0 compose code, and neither are a model of clarity and
simplicity. I can see why Seth didn't fix this, because it's hard.
Whiteboard: [nsbeta2+] → [nsbeta2+] ETA 7/13
Assignee | ||
Comment 12•24 years ago
|
||
fixed, for the case that the posting was started when a newsgroup/news message
was selected. I haven't put any of the fancy logic in that Phil describes. We
could leave that for another bug.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•24 years ago
|
||
whoops, I forgot to check in one file for this - this won't be fixed in today's
build. You'll have to wait for tomorrow's build.
Comment 14•24 years ago
|
||
Verified this is working on Linux & Windows builds (07-17-08/09-M17
commercial builds)for the new news profile
(migrated news currently has regression on Linux -- bug 45299)
But, I still cannot close this bug since problem (bug 19119) problem is still
occurring on secnews for ONLY Mac platform....updating whiteboard for the reason
of the verification.
Whiteboard: [nsbeta2+] ETA 7/13 → [nsbeta2+] Wait Cartman on mac in order to verify/close this bug
Comment 15•24 years ago
|
||
Verified on all the platforms:
WiNT 07-20-09-M17 commercial build
Linux 07-20-08-M17 commercial build
Mac 07-20-08-M17 commercial build
Seamonkey won't post the same message from the different news server even
thought they are same newsgroup names now. Marking as verified!!
Status: RESOLVED → VERIFIED
Whiteboard: [nsbeta2+] Wait Cartman on mac in order to verify/close this bug → [nsbeta2+]
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•