Re: Use of message disposition notification

"Charles Lindsey" <chl@clerew.man.ac.uk> Wed, 15 April 2009 16:13 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3481C3A69CC for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 15 Apr 2009 09:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.939
X-Spam-Level:
X-Spam-Status: No, score=-4.939 tagged_above=-999 required=5 tests=[AWL=-0.940, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWqazPfHsT16 for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 15 Apr 2009 09:13:58 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id A4B8C3A693B for <usefor-archive@ietf.org>; Wed, 15 Apr 2009 09:13:57 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n3FGCTKT037896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Apr 2009 09:12:29 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n3FGCTDg037895; Wed, 15 Apr 2009 09:12:29 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from v-smtp-auth-relay-5.gradwell.net (v-smtp-auth-relay-5.gradwell.net [79.135.125.99]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n3FGCHTC037866 for <ietf-usefor@imc.org>; Wed, 15 Apr 2009 09:12:27 -0700 (MST) (envelope-from news@clerew.man.ac.uk)
Received: from [80.175.135.89] ([80.175.135.89] helo=clerew.man.ac.uk country=GB ident=postmaster#pop3*clerew$man*ac*uk) by v-smtp-auth-relay-5.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.290) id 49e6075e.1da6.e86 for ietf-usefor@imc.org; Wed, 15 Apr 2009 17:12:14 +0100 (envelope-sender <news@clerew.man.ac.uk>)
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id n3FGC5V6012341 for <ietf-usefor@imc.org>; Wed, 15 Apr 2009 17:12:05 +0100 (BST)
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id n3FGC4RW012336 for ietf-usefor@imc.org; Wed, 15 Apr 2009 17:12:04 +0100 (BST)
To: ietf-usefor@imc.org
Xref: clerew local.usefor:25037
Path: clerew!chl
From: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: Use of message disposition notification
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <KI5A03.25H@clerew.man.ac.uk>
Content-Transfer-Encoding: 8bit
X-Newsreader: NN version 6.5.2 (NOV)
References: <D2BCD434C62C4A78B1C6D5DC08D75CD2@Iulius> <87bpr8cpyu.fsf@windlord.stanford.edu> <KHs9E5.5xC@clerew.man.ac.uk> <96088B3EFAFE49899F643996FBEC91B5@Iulius> <KHu8tA.8MM@clerew.man.ac.uk> <5BD46A76620B4AAAB7267B8C2BD06547@Iulius>
Mime-Version: 1.0
Date: Wed, 15 Apr 2009 13:40:51 +0000
Lines: 37
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

In <5BD46A76620B4AAAB7267B8C2BD06547@Iulius> Julien ÉLIE <julien@trigofacile.com> writes:

>Hi Charles,

>> Cancel-Lock is not formally defined anywhere

>Yet, this draft can be a good starting point:
>    http://www.eyrie.org/~eagle/usefor/drafts/draft-ietf-usefor-cancel-lock-01.txt


>> hence I know of no news-server that ever looks at it

>news.individual.net does not honour cancels and supersedes
>if there is no valid Cancel-Key: header.
>    http://www.individual.net/faq.php#1.12
>    http://groups.google.co.uk/group/alt.usenet.news-server-comparison/msg/7e6d4792819ad90f


Ah! I am a NIN customer, but they never told me about it :-( .

But on looking at the FAQs that I regularly post, I see that they have
been adding Cancel-Locks and Cancel-Keys to them, and they seem to have
worked.

Is that draft-ietf-usefor-cancel-lock-01.txt still a correct description
of the algorithm as it is now implemented?

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131            Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5