Paul a émis l'idée suivante :
On 5/4/2022 6:07 AM, ***@free.fr wrote:
Hi,
I hope it's the good groop for this plaint.
Your server accept since few days the cancels from "miakibot2".
A lot of cancel from this robot is not legitimate cancel.
But it's a cancel war againt one person.
A lot of French users are not for these cancels which are not
consensual
You should know that that the "miakibot" has already deleted last year
more than 3600 messages from another person (Pierre) in a very abusive
way. This time his target is "Neo".
Please, block these cancellations of the miakibot of which a great part
is abusive or block the cancellations of the servers from which these
abusive cancellations come from (server ALPHANET which does not want to
do anything and produce)
sincerely yours,
Examples of recent abusives cancels:
Message-ID:
<cancel.t4h2np$18b$***@dont-email.me>
<cancel.t4h4hj$gkt$***@dont-email.me>
You want eternal-september.org
The address for correspondence/email is:
mail-complaints-to = "***@eternal-september.org"
******************************************************
http://al.howardknight.net/?STYPE=msgid&MSGI=%3Ct4h2np%2418b%241%40dont-email.me%3E
Message-ID: <t4h2np$18b$***@dont-email.me>
Injection-Info: reader02.eternal-september.org;
posting-host="567ad90b4411d4bd307d983d52254db1";
logging-data="1291";
mail-complaints-to="***@eternal-september.org";
posting-account="U2FsdGVkX1/8bpji8EfGproVjviyQY8m"
User-Agent: MacCafe/2.07 (4D18) (macOS 12.3.1 (21E258) - iMac18,3)
Cancel-Lock: sha1:Td+2MwxvrwXpMoggioJJMbqSdR0=
\
sha256:OVzsl0bFZRe8ztbKy3K5lwze9EBUmN29DL0/HTMK1LY=
\___ This is not normal
sha1:H8zxdiknN5VL6cy1IDbFMe6TrQs= /
https://en.wikipedia.org/wiki/Control_message
https://web.archive.org/web/20070502013009/http://tools.ietf.org/html/draft-ietf-usefor-cancel-lock-01
"3.1 Adding an initial "Cancel-Lock: " header to a
proto-article... <=== Does not explain it
Your client did not add excess cancel-locks to your complaint message.
As a result, perhaps try posting via AIOE and see if the cancelbot and
Rogue Server in the path, are damaging posts in that sequence
as well (somehow). AIOE does not appear to be adding a
Cancel-Lock header, and your posting might well survive.
Info posted on your cancel itself.
https://groups.google.com/g/fr.soc.politique/c/7O4QLZ9mM20/m/Omasx5f2AAAJ
Paul
I am not sure to understand excatly what you said.
I make a test to send a message from AIOE
It was cancelled by the miakibot too.
The rogue cancel message:
----------------------------------------------------------------------
Path:
aioe.org!news.alphanet.ch!alphanet.ch!miakibot!byreferences!cyberspam!not-for-mail
From: miakibot3 <***@miakinen.net>
Organization: miakibot
Subject: cmsg cancel
<***@consensus-omnium>
Control: cancel <***@consensus-omnium>
Date: Wed, 04 May 2022 23:42:15 +0200
Archive: No
X-No-Archive: Yes
Message-ID:
<***@consensus-omnium>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Followup-To: poster
X-Original-From: LaLibreParole <***@laposte.net>
Newsgroups: fr.usenet.abus.d
X-Original-Subject: Re: La philosophie du cancel sur Usenet
X-Original-Date: Wed, 04 May 2022 23:40:25 +0200
X-Original-Message-ID:
<***@consensus-omnium>
Xref: aioe.org control.cancel:1582821
Response to a cancelled article (byreferences)
------------------------------------------------------------------------
I Think the problem is not the source message, or cancel-lock but
the acceptance of the rogue cancel from ALPHANET server,
The abusive user on this serveur is: "<***@miakinen.net>"
But the ALPHANET server promote these rogues cancels.
This is why i write to server which newly accept these abusives
cancels of the miakibot2 or miakibot3.
Until April 29 or 30 "aioe" did not accept these cancels.
But now "aioe" accept them.
Plesae, stop to accept these rogues cancels.
sincerely yours,