Re: Rogue cancel from miakibot
Paul <[email protected]>
| Newsgroups | aioe.news.helpdesk,eternal-september.support |
|---|---|
| Organization | Aioe.org NNTP Server |
| Message-ID | <[email protected]> |
On 5/4/2022 6:07 AM, [email protected] 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: > <[email protected]> > <[email protected]> You want eternal-september.org The address for correspondence/email is: mail-complaints-to = "[email protected]" ****************************************************** http://al.howardknight.net/?STYPE=msgid&MSGI=%3Ct4h2np%2418b%241%40dont-email.me%3E Message-ID: <[email protected]> Injection-Info: reader02.eternal-september.org; posting-host="567ad90b4411d4bd307d983d52254db1"; logging-data="1291"; mail-complaints-to="[email protected]"; 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