On Thu, 01 Jan 2015 20:56:00 -0800, drek <none@none.invalid> wrote:
>On Sat, 20 Dec 2014 22:14:31 -0800, drek
>wrote:<npbb9ahtp2oct4dv5jognk7pc5jmv320rl@4ax.com>
>
>>If by corrected you mean the way some versions of Powerpost can
>>re-post individual articles, that shouldn't break the NZB. I believe
>>re-posting an article uses the same Message-ID and it simply
>>supersedes the original (it gets overwritten). Naturally if it doesn't
>>exist it simply gets stored. In either case the MID is unchanged and
>>the NZB is still valid.
>>
>Turns out the original MID does not get reused. I did some reading and
>a few tests. I also asked in n.s.n. and Ralph Fox wrote a good summary
>of supersedes with references:
>
>Re: How are supersedes and Message-ID being handled now?
>news.software.nntp
>M-ID: <6kabaa5v8r28uvmhcuucin2tieulk4gbh2@4ax.com>
http://nntp.software.news.groups.com.ru/18761-Re_How_are_supersedes_and_MessageID_being_handled_now
This is going off on a tangent, as to what happens when an NZB is
posted before the actual post, or corrections or reposts are later
done.
Message Identification (MID), if the same, is rejected as a duplicate
in server to server communications.
"Supersede" is a cancel and replace, also rejected for security
reasons.
Powerpost does MID+1 which allows the repost to propagate through the
server system.
Newsreaders so not care about the MID and use the requested Subject
line to determine the requested MID. Except NZB's, which ask for
specific MIDs. An old NZB gets old message and a new (more recent)
NZB gets the new message.
As an example, Binsearch creates a new NZB using the most recent
subject lines to list the most recent MIDs which are used by
newsreaders to download the most recent file set.
Not stating facts here, but above is likely close to what happens.
|
|