Closed
Bug 32715
Opened 24 years ago
Closed 24 years ago
Reply-all to mozilla groups goes to mailing list AND newsgroup
Categories
(MailNews Core :: Composition, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla0.9
People
(Reporter: akkzilla, Assigned: bugzilla)
Details
(Whiteboard: [nsbeta1+])
The mozilla lists are available as mailing lists AND newsgroups, e.g. mozilla-seamonkey@mozilla.org and netscape.public.mozilla.seamonkey. If I use mozilla to reply-all to a message that I read on the mailing list version of one of these groups, the To lines will have both the mailing list and the newsgroup in them. 4.x only has the mailing list; it doesn't try to include the newsgroup if I'm replying to a mail article. On the face of it, this seems like a good thing (don't throw away information), but in practice it means that anyone casually using mozilla to reply-all to a message on our mozilla lists will end up posting twice. Or would if it worked: but actually, the news version fails: it bounces back with the message: Reporting-MTA: dns; gila.mozilla.org Received-From-MTA: DNS; h-205-217-237-47.netscape.com Arrival-Date: Tue, 21 Mar 2000 13:44:35 -0800 (PST) Final-Recipient: RFC822; <mozilla-seamonkey@mozilla.org>Action: expanded (to multi-recipient alias) Status: 2.0.0 Last-Attempt-Date: Tue, 21 Mar 2000 13:44:42 -0800 (PST) Final-Recipient: RFC822; <mozilla-seamonkey@mozilla.org> X-Actual-Recipient: RFC822; netscape.public.mozilla.seamonkey@gila.mozilla.org Action: failed Status: 5.5.0 Last-Attempt-Date: Tue, 21 Mar 2000 13:44:42 -0800 (PST) Ideally, we should do something that will cause users not to post twice AND not to get an error message. I'm not sure what this "something" is, but the safe bet might be to do what 4.x does and not try to put newsgroups in the headers of mail replies.
Comment 2•24 years ago
|
||
Minor UI fixups to M18. If this is incorrect, please adjust.
Target Milestone: M17 → M18
Moving to future milestone. Can the user simply wipe out the incorrect address in the addressing widget? If I'm missing something here - like we end up getting a high failure rate for sending news messages - then please include this information in the bug, and move the target milestone back to m18.
Target Milestone: M18 → Future
Reporter | ||
Comment 4•24 years ago
|
||
This bug makes mozilla unusable for replying to mail that was sent to a mozilla newsgroup but was read via mail; it ends up having both in the header, editing them down doesn't work, it sends out two copies, then one of the copies bounces because it has the wrong headers. When I have to reply to a message like that, I have to bring up 4.x. I can't believe futuring this bug -- if anything, it should be considered dogfood (it is, for anyone who needs to do a lot of replying to mozilla group postings).
Reporter | ||
Comment 5•24 years ago
|
||
Trying again to add keywords -- attempts to add keywords with mozilla have been failing frequently for me.
Keywords: dogfood
Target Milestone: Future → M18
Comment 6•24 years ago
|
||
Mail Triage is marking [nsbeta3-]
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
Comment 8•24 years ago
|
||
JF, do we have anyway of knowing that we should be posting this for the newsgroup?
Whiteboard: [nsbeta3-] → [nsbeta3-][NEED INFO]
Comment 9•24 years ago
|
||
marking nsbeta1+ and moving to mozilla0.8 We shouldn't be filling in newsgroups in the To: header and then appending the domain.
Comment 10•24 years ago
|
||
Is this still happening? Moving to mozilla0.9 in case it is.
Target Milestone: mozilla0.8 → mozilla0.9
Assignee | ||
Comment 11•24 years ago
|
||
we use to have some problem with the addressing widget a while ago due to an XBL bug but now everything is back to normal. The behavior of the replyAll was different from platform to platform in 4.x but now it's consistent: it always reply to all recipients and groups. Soon you will be able to say reply to group or reply to group and sender (see bug 17796 for more info)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
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
•