11045 - Support news `supersede` (header field)

Status: NEW

(MailNews Core :: Backend, enhancement)

Description

[(not reading, please use [e-mail] instead)]

marking m15

Comment 1

[Phil Peterson]

Bulk-resolving requests for enhancement as "later" to get them off the Seamonkey
bug tracking radar. Even though these bugs are not "open" in bugzilla, we
welcome fixes and improvements in these areas at any time. Mail/news RFEs
continue to be tracked on http://www.mozilla.org/mailnews/jobs.html

Comment 2

[Phil Peterson]

Reopen mail/news HELP WANTED bugs and reassign to [e-mail]

Comment 3

[Garth Wallace]

This is part of GNKSA (http://www.newsreaders.com/gnksa/gnksa.txt) section 
13: "Allow users to both cancel and supersede their own articles (and
    _no_ others!)":

> Any software that posts news SHOULD provide a command that the user can
> invoke to cancel her own articles.  It SHOULD also provide the option to
> supersede the user's own articles.  The software MUST guarantee that
> the user cannot cancel or supersede other people's articles, as far as
> possible.

As such, it blocks bug #12699. Marking dependency.

Comment 4

[Olav Vitters]

*** Bug 155331 has been marked as a duplicate of this bug. ***

Comment 5

[Ronald Killmer]

Does this bug still impact Seamonkey ?

With Tunderbird 1.5.0.10 I can cancel my own messages on news.annexcafe.com server as it is configured to accept cancel requests.

Not knowing about supersede I wonder how this is supposed to be done.

Based on the cancel function, should this bug be marked as fixed ?

Comment 6

[Kamil Jonca]

No. Supersede is "little different" functionality. :)

Comment 7

[Jens Müller (:tessarakt)]

Any progress on this? :-(

Does not sound very difficult ... It's just one header plus some UI ...

For what exactly is "helpwanted"?

Comment 8

[Ronald Killmer]

(In reply to comment #7)
> Does not sound very difficult ... It's just one header plus some UI ...
> 
> For what exactly is "helpwanted"?

Helpwanted means any one with an interest in this bug and has resources to invest in a fix, is free to contribute. The development teams have there resources fully committed to higher priority bugs, yet they agree this bug has value. If anyone creates a patch, the Devs will assist with integrating it into the code base.

Comment 9

[Jens Müller (:tessarakt)]

It does not really block bug 520784, IMO. This bug is about creating the header, 520784 is about using/analyzing it.

Comment 10

[John David Galt]

Bug 16925 created the ability (and its comments tell how) to post news messages with a Supersedes: or any other header.  What, if anything, remains to do?

Comment 11

[Jens Müller (:tessarakt)]

(In reply to comment #10)
> Bug 16925 created the ability (and its comments tell how) to post news messages
> with a Supersedes: or any other header.  What, if anything, remains to do?

I browsed through the comments of that bug. As I see it, the fix there allows to specify headers (via a pref only?) which you can then manually set in a new message.

For Supersedes, something more/different is needed:

* There should be an option "Supersede" in the context menu of a message (or somewhere else, but per message!). Let's call that message "original message".
* When that option is used, the "new" message will have the following properties:
 - Newsgroups and account are the same as in the original message.
 - References: are kept.
 - The Supersedes: header is the Message-ID of the original message.
 - The text will initially be that of the original message.

Supersede will only be allowed when Cancel is allowed as well.

For any further details, please consult the IETF draft.

Comment 12

[Jens Müller (:tessarakt)]

The specs:

http://tools.ietf.org/html/draft-ietf-mailext-new-fields-14 (removed from -15 because they wait for usefor (the next one))

http://tools.ietf.org/html/draft-ietf-usefor-usefor-12#section-3.2.12

Comment 13

[Karsten Düsterloh]

It's really just a matter of someone writing a patch, everything else is already there. But since a workaround exists (add Supersedes to mail.compose.other.headers, choose Supersedes header when composing and copy over the MID of the old posting) and Supersedes is rarely used feature, this hasn't high priority. Personally, I'd love to see a patch (for SeaMonkey at least *g*) here and help drinving it home, if needed. After all, it's actually just "Edit as New" plus an additional header...

Comment 14

[Jens Müller (:tessarakt)]

(In reply to comment #13)
> But since a workaround exists (add Supersedes to
> mail.compose.other.headers, choose Supersedes header when composing and copy
> over the MID of the old posting) and Supersedes is rarely used feature, 

Haha ... Imagine why ... The ugly workaround Cancel&Repost is not so rarely used.

Comment 15

[Jens Müller (:tessarakt)]

Now an RFC and draft Internet Standard: http://tools.ietf.org/html/rfc5536#section-3.2.12

Comment 16

[Stéphane Grégoire (yamo)]

This bug may be resolved by using the same functionality as "Open as a new message"/("Modifier comme un nouveau message" in my client), by picking the message-ID and putting it in the supersedes header with brakes (<>).

Like this :  http://al.howardknight.net/msgid.cgi?STYPE=msgid&A=0&MSGI=+%3Cl7cd8c%24i60%242%40usenet.pasdenom.info%3E 

But I don't know how helping doing that.

Comment 17

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/923b8ee68241
[fenix] For https://github.com/mozilla-mobile/fenix/issues/11045: Add reader mode to urlView