522294 - Duplicate Newsgroups Not Detected When Cross-Posting, resulting in duplicate posts

Status: REOPENED

(MailNews Core :: Composition, defect)

Description

[David E. Ross]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18
Build Identifier: Thunderbird 2.0.0.23 (Windows/20090812)

An announcement was cross-posted to the following newsgroups:  mozilla.dev.apps.seamonkey, mozilla.support.seamonkey, mozilla.dev.apps.seamonkey, mozilla.dev.planning, mozilla.support.mozilla-suite, netscape.public.mozilla.seamonkey. The duplicate appearance of mozilla.dev.apps.seamonkey was not detected.  

In <news://news.mozilla.org:119/mozilla.dev.apps.seamonkey>, see the thread with the Subject: SeaMonkey 2.0 Release Candidate 1 (original message dated Sat, 10 Oct 2009 18:41:02 +0200, NNTP posting date Sat, 10 Oct 2009 11:41:04 -0500).  Although the original message was posted via SeaMonkey 2.0, replies posted via Thunderbird showed the same problem.  


Reproducible: Always




This might also be a problem with E-mail, where an E-mail address is duplicated.  

I would suggest that, instead of silently removing the duplicate address, Thunderbird should have a warning popup asking whether the message should be sent.  This would allow intentional duplicate addresses while also allowing users to remove duplicates from the address list.  

Note that, for this announcement, cross-posting was indeed appropriate.  The sender of the original message intended (but forgot) to change the "Newsgroup:" for the duplicate to "Follow-up to:".  My suggested fix would have alerted the originator that he indeed did forget to make that change.

Comment 1

[David E. Ross]

The setting of Component to "Networking: NNTP" implies this is a newsgroup-only problem.  I indicated in the original description that this might also be an E-mail problem.  Has that been investigated?  If this is also an E-mail problem, the Component should instead be merely "Networking".

Comment 2

[Joshua Cranmer [:jcranmer]]

Actually, to be fair, it's a problem with the compose code not checking its input fields.

Most NNTP servers shouldn't care about duplicate newsgroups, unless you get obstinate, stupid mail/news gateways.

Comment 3

[Wayne Mery (:wsmwk)]

this is not specific to tb2.  I recently posted with a duplicate newsgroup name, and it posted twice.

Comment 4

[Tristan Miller]

Not reproducible for me with 140.2.0esr. Given the age of this bug, I'll boldly close it as WORKSFORME. Feel free to reopen it if you can still reproduce it.

Comment 5

[Alfred Peters [:infofrommozilla]]

Attachment: bug522294.png

=> <109jb8i$3g57r$[e-mail]>

Newsgroups: misc.test,misc.test

Comment 6

[Alfred Peters [:infofrommozilla]]

Whether this results in a duplicate article depends on the server.

However, the real problem is the duplicate group. This should be removed before sending at the latest.

TB should not accept it as input in the first place.