Open Bug 35338 Opened 25 years ago Updated 2 years ago

Overzealous blocking of cross-posting to multiple hosts

Categories

(MailNews Core :: Backend, defect, P5)

x86
All

Tracking

(Not tracked)

Future

People

(Reporter: sspitzer, Unassigned)

References

(Blocks 2 open bugs)

Details

two parts to this bug: the first part: the code that determines if you are trying to cross post to multiple hosts is too strict, and reports false positives. the second part: what's worse, is the error message never pops up, so you don't know why the message didn't post or why the compose window won't go away.
I have the fix for at least part of this bug in my tree at home. will check in for m16.
Status: NEW → ASSIGNED
Priority: P3 → P1
Summary: [NEWS] overzealous blocking of cross-posting to multiple hosts → [NEWS] overzealous blocking of cross-posting to multiple hosts
Target Milestone: --- → M16
ok, the good news is the alert now shows up if you attempt to cross post to multiple servers. the bad news is we are still being over-zealous.
Seth, I think you fixed the P1 part of this. The overzealous part doesn't seem critical for M16. If you disagree, please explain in the bug and move it back.
Target Milestone: M16 → M17
now that we have hostinfo.dat support, I can fix this.
this should be fixed for beta2.
Keywords: nsbeta2
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
QA Contact: lchiang → laurel
Do we have a reproducible case for this? Probably wouldn't hold beta2 for this unless we know how to reproduce it.
removing nsbeta2+ and asking for consideration to cut from beta2.
Whiteboard: [nsbeta2+]
Putting on [nsbeta2-] radar. Not critical to beta2. Adding "relnote" keyword for PR2 release.
Keywords: relnote
Whiteboard: [nsbeta2-]
Will look at this and see if it warrants release note in beta2. Changed relnote to relnote2
Keywords: relnoterelnote2
Keywords: relnote2
Well, I don't know about the cases Seth was referring to, but in the cases I've tried I do see an alert telling me I can only post to one server at a time. I tried posting a message to the same server, but specifying one group by group name "netscape.test" and the other by url (to the same server) "news://news.mozilla.org/netscape.public.test. It errored, but told me why it was complaining and as soon as I changed back to group name I was ok and posting posted. Will wait for seth's comments later, removing relnote.
Using both the M17 build and the M18 nightlies, I can't post to more than 1 group even in the same server (when replying to messages, at least. Haven't tried to post a new message.). And, most annoying, the message telling I can't post to more than one server pops up one time for each group in the list...
QA Contact: laurel → stephend
marking nsbeta1-.
Keywords: nsbeta2nsbeta1-
Whiteboard: [nsbeta2-]
clearing milestone, m17 and m18 are meaningless now. these need to be triages along with the rest.
Target Milestone: M17 → ---
adding phil, he just got bit by this. I just talked it over with bienvenu, and I'll fix it to do what we did in 4.x
Target Milestone: --- → mozilla0.9
removing mozilla0.9 and nominating for nsbeta1
Keywords: nsbeta1-nsbeta1
Target Milestone: mozilla0.9 → Future
marking nsbeta1- but if you have the fix (I saw something go into the perf branch) then check it in.
Keywords: nsbeta1nsbeta1-
Blocks: 77147
This happens in 0.8.1. I get a warning when trying to reply to a message that was crossposted in n.p.m.wishlist and n.p.m.ui.
*** Bug 77147 has been marked as a duplicate of this bug. ***
Blocks: 76449
This violates GNKSA section #3a: "When creating either a new article or a followup, the user MUST be allowed to specify multiple newsgroups, and the software MUST cross-post (not multi-post) to them if more than one is specified". Blocks bug #76449 and bug #12699.
Blocks: gnksa
Comments From Marcelo Vanzin 2000-08-11 15:17: > Using both the M17 build and the M18 nightlies, I can't post to more than 1 > group even in the same server (when replying to messages, at least. Haven't > tried to post a new message.). I see the same. I have several news servers in my profile. Marcelo, Garth, you too? If the bug happens only in this case, I don't think that it blocks GNAKSA compliance.
nope, only one news server for me (news.mozilla.org, specifically)
we never multi-post to multiple servers. we do allow cross posting. the problem is if you have multiple servers set up, the code I wrote can incorrectly determine that you are attempting to cross post to two servers and not allow you to post at all.
Seth, yes, that's exactly what I guessed. But that doesn't explain Garth's problem.
When you fix it, please make sure that I can cross-post, even if only one of the newsgroups appears in more than one of my servers, if that is not unreasonably hard to implement. E.g. I am subscribed to news.myisp.com mozilla.mail-news alt.netscape-sucks news.mozilla.org mozilla.mail-news mozilla.editor Now I cross-post to mozilla.mail-news and mozilla.editor. It should succeed, posting to news.mozilla.org.
garth: you only had one news server, right? were you subscribed to either group you attempted to post to? are you still able to reproduce this? please start a new bug on your problem. benb: your scenario is exactly the one I'll be trying to fix when I get some cycles for this bug.
I'm subscribed to wishlist but not ui. That's probably the problem.
garth, that should work fine. if you can still reproduce this, can you take this to another bug? we'll figure it out there.
Seth, we had some regression posting to two newsgroups on the same server (as noted in bug 77147), but today on both Mac and Linux, I can cross-post to netscape.test and netscape.public.test, so seems the regression was fixed and this bug can now return to its regular scope ;-) Sorry for the noise.
When 0.9 comes out I'll try to reproduce it. If it's still there, I'll file the new bug.
(This bug is quite terse, IMHO.) Can someone explain to me: * What's the expected behaviour? and * What's our current behaviour? Thanks.
Summary: [NEWS] overzealous blocking of cross-posting to multiple hosts → Overzealous blocking of cross-posting to multiple hosts
*** Bug 115205 has been marked as a duplicate of this bug. ***
Bug 115205 is distinguishable from this bug in that it has nothing to do with attempting to post to multiple servers. Bug 115205 is therefore not a dupe.
Testing with 0.9.9 branch, build 2002031108 I think bug 115205 and this one are more or less the same things. bug 115205 is reported as fixed, and indeed some situations are solved. If you try to cross-post to one group you are subscribed too and another you are not subscribed too, now you can. If you try to cross-post to one group that exist, and another that doesn't existe on your newsserver, you can and you have no warning. I don't consider this as ideal. I think you should be allowed to do that, but with a warning. Now any striking error in a cross-post will send your message to nowhere. But the problem is that despite that, the exact problem described in comment #22 is still there ! Steps to reproduce : - have an account on newsserver A and B. - be subscribed to both groups X and Y on server B, but only to group X on server A. - try to answer to a message on server B that is crossposted between X and Y. This will fail with the error "you can only send a message to one news server at a time". Don't close the message windows. - Remove the subscription to group X on server A. - Retry sending the message windows you didn't close. Now it works. It doesn't really seem to matter whether A is before B or not in your list of servers.
Looks like this and bug 54911 could really be the same problem and fix: bug 80542. Severity major and not w32 only.
No longer blocks: gnksa
*** Bug 172115 has been marked as a duplicate of this bug. ***
Any plans to make the newsreader usable by fixing this P1 bug?
OS: Windows NT → All
according to description 1 in bug 172115. when will it be fixed? (1.7a, Gecko/20040109)
Product: MailNews → Core
This bug still exists and is quite annoying. Using Mozilla 1.7.1, Gecko/20040707. I want the normal ability to crosspost -- without being forced to unsubscribe to every group I am crossposting to on my other news servers.
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Status: ASSIGNED → NEW
Filter on "Nobody_NScomTLD_20080620"
QA Contact: stephend → backend
Product: Core → MailNews Core
Priority: P1 → P5
Severity: normal → S3
Severity: S3 → S4
Blocks: gnksa
You need to log in before you can comment on or make changes to this bug.