• cmsg cancel

    From Zo@homenet@newsbill.net to alt.windows7.general on Thu Oct 22 16:31:58 2026
    From Newsgroup: alt.windows7.general

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Cancel Watcher@cancel.watcher@somewhere.on.usenet to alt.windows7.general on Thu Oct 22 17:45:26 2026
    From Newsgroup: alt.windows7.general

    Zo wrote:

    From: "Zo" <homenet@newsbill.net>
    Newsgroups: alt.windows7.general
    Subject: cmsg cancel <rgv4ng$pdm$1@news.mixmin.net>
    Control: cancel <rgv4ng$pdm$1@news.mixmin.net>
    Date: Thu, 22 Oct 2026 16:31:58 -0000 (UTC)
    Sender: Efye Good Guy Efye <Hello.World@example.com>
    Message-Id: <cancel.rgv4ng$pdm$1@news.mixmin.net>

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>


    Holy smoke Batman! It's a necro-cancel!

    The original message to be canceled was posted over 6 years ago.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From VanguardLH@V@nguard.LH to alt.windows7.general on Fri Oct 23 01:55:30 2026
    From Newsgroup: alt.windows7.general

    Cancel Watcher <cancel.watcher@somewhere.on.usenet> wrote:

    Zo wrote:

    From: "Zo" <homenet@newsbill.net>
    Newsgroups: alt.windows7.general
    Subject: cmsg cancel <rgv4ng$pdm$1@news.mixmin.net>
    Control: cancel <rgv4ng$pdm$1@news.mixmin.net>
    Date: Thu, 22 Oct 2026 16:31:58 -0000 (UTC)
    Sender: 0a+0+e Good Guy 0a+0+e <Hello.World@example.com>
    Message-Id: <cancel.rgv4ng$pdm$1@news.mixmin.net>

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>

    Holy smoke Batman! It's a necro-cancel!

    The original message to be canceled was posted over 6 years ago.

    I thought the Date header was a client-added header. That's how, for
    example, some joker can keep pushing his posts to the top of the list
    (most users have their clients sort new to old) by future-dating their
    posts. Presumably the headers were trimmed. There were no other
    datestamping headers, like NNTP-Posting-Date or Injection-Date?

    Mixmin is a sewer source that I filter out.

    https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-rfc5322bis-12/#name-date-and-time-specification
    Section 3.6.1 The Origination Date Field
    The origination date specifies the date and time at which the creator of
    the message indicated that the message was complete and ready to enter
    the mail delivery system. For instance, this might be the time that a
    user pushes the "send" or "submit" button in an application program. In
    any case, it is specifically not intended to convey the time that the
    message is actually transported, but rather the time at which the human
    or other creator of the message has put the message into its final form,
    ready for transport.

    Above found by looking at:

    https://www.iana.org/assignments/message-headers

    and looking at the Date entries. Both Internet messaging (email) and
    netnews use the same definition.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Fri Oct 23 04:06:37 2026
    From Newsgroup: alt.windows7.general

    On Fri, 10/23/2026 2:55 AM, VanguardLH wrote:
    Cancel Watcher <cancel.watcher@somewhere.on.usenet> wrote:

    Zo wrote:

    From: "Zo" <homenet@newsbill.net>
    Newsgroups: alt.windows7.general
    Subject: cmsg cancel <rgv4ng$pdm$1@news.mixmin.net>
    Control: cancel <rgv4ng$pdm$1@news.mixmin.net>
    Date: Thu, 22 Oct 2026 16:31:58 -0000 (UTC)
    Sender: N++N++N++N++N++N++ Good Guy N++N++N++N++N++N++ <Hello.World@example.com>
    Message-Id: <cancel.rgv4ng$pdm$1@news.mixmin.net>

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>

    Holy smoke Batman! It's a necro-cancel!

    The original message to be canceled was posted over 6 years ago.

    I thought the Date header was a client-added header. That's how, for example, some joker can keep pushing his posts to the top of the list
    (most users have their clients sort new to old) by future-dating their
    posts. Presumably the headers were trimmed. There were no other datestamping headers, like NNTP-Posting-Date or Injection-Date?

    Mixmin is a sewer source that I filter out.

    https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-rfc5322bis-12/#name-date-and-time-specification
    Section 3.6.1 The Origination Date Field
    The origination date specifies the date and time at which the creator of
    the message indicated that the message was complete and ready to enter
    the mail delivery system. For instance, this might be the time that a
    user pushes the "send" or "submit" button in an application program. In
    any case, it is specifically not intended to convey the time that the
    message is actually transported, but rather the time at which the human
    or other creator of the message has put the message into its final form, ready for transport.

    Above found by looking at:

    https://www.iana.org/assignments/message-headers

    and looking at the Date entries. Both Internet messaging (email) and
    netnews use the same definition.

    Some servers had "post in the future" protection, set to about two
    hours difference between the client and server. This might not be
    a "standard feature". I think I've received a "post in the future"
    result, just after booting back from Linux to Windows and not correcting
    my clock. At one time that might have been set to one hour difference, but various
    date issues in OSes (the OSes which are out of support and their
    TZData isn't correct) mean that the server admin has to adjust for
    the most meaningful result.

    I have seen messages in newsgroups, with dates that are grossly incorrect.
    It's true that has happened in the past. There could be messages from 1970.

    Paul


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to alt.windows7.general on Fri Oct 23 14:34:41 2026
    From Newsgroup: alt.windows7.general

    VanguardLH <V@nguard.lh> wrote:
    Cancel Watcher <cancel.watcher@somewhere.on.usenet> wrote:

    Zo wrote:

    From: "Zo" <homenet@newsbill.net>
    Newsgroups: alt.windows7.general
    Subject: cmsg cancel <rgv4ng$pdm$1@news.mixmin.net>
    Control: cancel <rgv4ng$pdm$1@news.mixmin.net>
    Date: Thu, 22 Oct 2026 16:31:58 -0000 (UTC)
    Sender: ?????? Good Guy ?????? <Hello.World@example.com>
    Message-Id: <cancel.rgv4ng$pdm$1@news.mixmin.net>

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>

    Holy smoke Batman! It's a necro-cancel!

    The original message to be canceled was posted over 6 years ago.

    I thought the Date header was a client-added header. That's how, for example, some joker can keep pushing his posts to the top of the list
    (most users have their clients sort new to old) by future-dating their
    posts. Presumably the headers were trimmed. There were no other datestamping headers, like NNTP-Posting-Date or Injection-Date?

    IIRC, News servers are configured to reject too old articles. IIRC, a
    week or two weeks. (I used to run an INN one, but it's too long ago to
    remember the details of this.)

    Anyway, this article's Injection-Date is just 5 minutes later.

    But more to the point, this article is a multi-part message with a
    text/html part, so it should never have been posted to these groups.

    See the 'message source' at

    <https://usenet.id/rgv4ng$pdm$1@news.mixmin.net>

    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Cancel Watcher@cancel.watcher@somewhere.on.usenet to alt.windows7.general on Fri Oct 23 14:46:36 2026
    From Newsgroup: alt.windows7.general

    VanguardLH wrote:
    Cancel Watcher <cancel.watcher@somewhere.on.usenet> wrote:
    Zo wrote:

    From: "Zo" <homenet@newsbill.net>
    Newsgroups: alt.windows7.general
    Subject: cmsg cancel <rgv4ng$pdm$1@news.mixmin.net>
    Control: cancel <rgv4ng$pdm$1@news.mixmin.net>
    Date: Thu, 22 Oct 2026 16:31:58 -0000 (UTC)
    Sender: Efye Good Guy Efye <Hello.World@example.com>
    Message-Id: <cancel.rgv4ng$pdm$1@news.mixmin.net>

    This message was cancelled by Zo

    Original message header:
    From: =?UTF-8?B?8J+YiSBHb29kIEd1eSDwn5iJ?= <Hello.World@example.com>
    Subject: [News] Russians have found an easy way to kill millions
    Date: Tue, 11 Aug 2020 18:00:30 -0400
    Newsgroups: alt.comp.os.windows-10,alt.windows7.general,microsoft.public.windowsxp.general,alt.comp.os.windows-xp,alt.comp.os.windows-8
    Message-ID: <rgv4ng$pdm$1@news.mixmin.net>

    Holy smoke Batman! It's a necro-cancel!

    The original message to be canceled was posted over 6 years ago.

    I thought the Date header was a client-added header. [...tl;dr;...]
    There were no other datestamping headers, like NNTP-Posting-Date or Injection-Date?

    My post shows the Message-IDs both of the cancel and of the the original message to be canceled. If you PYFO and put each of the Message-IDs
    into <https://usenet.id/> or a similar site, you will see that:

    ruA The cancel message has Injection-Date: Thu, 22 Oct 2026 16:31:59
    -a +0000 (UTC)

    ruA The original message to be cancelled has Injection-Date: Tue, 11
    -a Aug 2020 22:05:37 -0000 (UTC)

    It *is* an actual necro-cancel.


    [...TL;DR;...]


    --- Synchronet 3.22a-Linux NewsLink 1.2