Deutsch   English   Français   Italiano  
<teokin$133c0$1@news.trigofacile.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!reader01.eternal-september.org!news.trigofacile.com!.POSTED.176.143-2-105.abo.bbox.fr!not-for-mail
From: =?UTF-8?Q?Julien_=c3=89LIE?= <iulius@nom-de-mon-site.com.invalid>
Newsgroups: fr.comp.usenet.serveurs
Subject: Re: Annulation pour autrui avec Cancel-Lock
Date: Wed, 31 Aug 2022 23:41:43 +0200
Organization: Groupes francophones par TrigoFACILE
Message-ID: <teokin$133c0$1@news.trigofacile.com>
References: <te1sug$8o2$2@rasp.pasdenom.info>
 <te1t1r$1aq$1@ns507557.dodin.fr.nf> <te1t76$8o2$4@rasp.pasdenom.info>
 <ac19gh9q9d5tkr9eufqcbqesfooqrp7nr6@consensus-omnium>
 <te21r7$j5a$1@rasp.pasdenom.info> <te274s$toq$2@shakotay.alphanet.ch>
 <te2ir6$rv2$1@rasp.pasdenom.info> <te3164$c9v$1@shakotay.alphanet.ch>
 <te3919$ft3$1@rasp.pasdenom.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 31 Aug 2022 21:41:43 -0000 (UTC)
Injection-Info: news.trigofacile.com; posting-account="julien"; posting-host="176.143-2-105.abo.bbox.fr:176.143.2.105";
	logging-data="1150336"; mail-complaints-to="abuse@trigofacile.com"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.12.0
Cancel-Lock: sha1:U1rrxR7cVeQc1UBa/YneXeenSs4= sha256:4+X4RMwP/hgbEnj76VtLB4NyBq0aXzqeGjw4ZmOuMzE=
	sha1:pZ8aYs65qY9xdwtkm4/FmJHi1LM= sha256:zTHz4lvDdWKnjy7x4sOsLoaJSR30pBNXgLxPbgfxHEg=
In-Reply-To: <te3919$ft3$1@rasp.pasdenom.info>
Bytes: 3130
Lines: 37

Bonsoir Stéphane,

> Par contre inews est pointilleux il refuse le post car le cancel est pour
> autrui.

C'est une règle de gestion qu'inews ne devrait pas mettre en œuvre 
(contraire aux RFC).
Pour info, c'est corrigé dans INN 2.7.0. En implémentant la gestion 
native du Cancel-Lock dans INN, j'ai fait une passe sur le fonctionnel 
d'inews. Extrait du journal des modifications :

The refusecybercancels and verifycancels parameters have been removed 
from inn.conf.  Besides, inews no longer checks if the From or Sender 
header fields of a cancel or supersede request match the ones of the 
original article being withdrawn.  All of these were either inefficient 
or inexact checks.

A new -E flag can now be given to inews to silently discard empty 
articles, instead of bailing out with an error.  Another new -m flag 
permits setting the Message-ID instead of letting inews generate one. 
And a third new flag, -Y, forces inews to authenticate to the remote 
news server even if not asked to.

inews no longer adds a Sender header field nor overwrites an existing 
one in articles it processes if the new -P flag is used.  The Path 
header field, if unset, no longer systematically contains the path 
identity of the local news server (you may want to add it manually with 
the -x flag, if needed).  Finally, inews also no longer adds the 
obsolescent Lines header field.


Cet utilitaire est très pratique :-)

-- 
Julien ÉLIE

« Les soucis d'aujourd'hui sont les plaisanteries de demain. Rions-en
   donc tout de suite. » (Henri Béraud)