Open
Bug 27768
Opened 25 years ago
Updated 2 years ago
Warn user of crossposts when replying
Categories
(MailNews Core :: Composition, enhancement, P3)
MailNews Core
Composition
Tracking
(Not tracked)
NEW
Future
People
(Reporter: gwalla, Unassigned)
References
(Blocks 2 open bugs)
Details
It would be a good idea if, in the case of a follow-up to a crosspost, Mozilla
would warn the user that the follow-up will be sent to more than one group. This
would only happen if the user hasn't edited the newsgroup line (in which case it
can be inferred that the user is aware of its contents). I can't count the
number of times I've posted a reply, then realized later that I've just spammed
a bunch of groups I didn't intend to. This could also cut down on multipost
trolls, whose posts can turn into huge threads very quickly.
On a related note, it would be nice if Mozilla would warn the user if the group
from which the original post is being read is not in the "Follow-Up:" line when
following up. Possible options at that juncture include "OK, sure, go ahead
anyway", "follow up to suggested groups and <current group>", and "follow up
just to this group"
Comment 1•25 years ago
|
||
A way of solving both these problems in a single dialog would be to ask `Are you
sure you want to send this message to all these groups?', with a series of
(initially checked) checkboxes (scrollable, if the number of groups is large)
showing all the groups that have been specified.
The original group (the one the user was reading when they hit Reply) would be
shown at the top of the list, and would be initially unchecked if it had not been
included in the followup-to header of the replied-to message. (The rest of the
groups would ideally be shown in alphabetical order.)
The sticky part of this feature is that it requires that Mozilla remember which
group the message being replied to had been posted in, even when the reply was
saved as a draft and returned to later. So you'd probably want a temporary
X-Original-Group: header which was saved with a draft, but deleted upon sending
after it had been used to determine whether the warning dialog was necessary.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17
Comment 2•25 years ago
|
||
Seth, do you want to take care on this bug?
Reporter | ||
Comment 4•24 years ago
|
||
Since M20 has ceased to potentially exist, could this bug get a new milestone
assigned?
Reporter | ||
Comment 5•24 years ago
|
||
I think this is a GNKSA issue. Specifically, standard 3b: "Posting software
SHOULD prevent the user from excessive cross-posting, or at least warn against it."
The GNKSA goes on to explain: "If posting to a very large number of groups, the
user SHOULD either be forced or strongly suggested to set a "Followup-To"
header. Such a header must be subjected to restrictions that are at least as
strict as those imposed on "Newsgroups:". " While not exactly equivalent, fixing
this would probably accomplish that, unless the GNKSA reviewer is really picky
and decides that clicking in the newsgroup line is insufficient to show
awareness of the message's destination. Adding bug #12699.
Blocks: gnksa
Reporter | ||
Comment 6•24 years ago
|
||
Ugh. I don't know what I was smoking when I wrote that second paragraph. While
this bug would address GNKSA section 3b (warning about crossposts), it doesn't
have anything to do with *setting* followup-to and therefore does not address
section 3c. That would be a separate bug.
Updated•23 years ago
|
Target Milestone: --- → mozilla0.9.6
Updated•23 years ago
|
Target Milestone: mozilla1.0 → Future
Comment 8•22 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Updated•21 years ago
|
Summary: [RFE] Warn user of crossposts when replying → Warn user of crossposts when replying
Updated•20 years ago
|
Blocks: usenetiquette
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: huang → composition
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•