Superseding trick not working

Superseding trick not working

[Karl Eichwalder]

At the moment, I'm not able to supersede an article:

First, I tried the trick described in the manual:

       If you have just posted the article, and change your mind right away,
    there is a trick you can use to cancel/supersede the article without
    waiting for the article to appear on your site first.  You simply return
    to the post buffer (which is called `*sent ...*').  There you will find
    the article you just posted, with all the headers intact.  Change the
    `Message-ID' header to a `Cancel' or `Supersedes' header by
    substituting one of those words for the word `Message-ID'.  Then just
    press `C-c C-c' to send the article as you would do normally.  The
    previous article will be canceled/superseded.

But Gnus complains:

Debugger entered--Lisp error: (error "Denied posting -- multiple copies")
  signal(error ("Denied posting -- multiple copies"))
  error("Denied posting -- multiple copies")
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit)

Going the old `S s' way, Gnus wants to know a "Canlock" thingie?
What's that?  I've never setup such a password.

My Gnus is a little bit dated, though...

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Superseding trick not working

[Reiner Steib]

On Tue, Jan 14 2003, Karl Eichwalder wrote:

> Going the old `S s' way, Gnus wants to know a "Canlock" thingie?

,----[ GNUS-NEWS ]
| ** Gnus supports Cancel Locks in News.
| 
| This means a header "Cancel-Lock" is inserted in news posting. It is
| used to determine if you wrote a article or not (for
| cancelling/superseding).  The behaviour can be changed by customizing
| `message-insert-canlock'.
`----

> What's that?  I've never setup such a password.

It should be stored in your `custom-file', usually ~/.emacs, unless
your distributor has -ehm- different opinions concerning Emacs init
files, SCNR. ;-)  But, IIRC, it should never be necessary to type it
for canceling or superseding messages.

> My Gnus is a little bit dated, though...

After updating, you'll find more info in <info://message/Canceling+News>.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

Re: Superseding trick not working

[Karl Eichwalder]

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

Thanks for the pointer!

> It should be stored in your `custom-file', usually ~/.emacs, unless
> your distributor has -ehm- different opinions concerning Emacs init
> files, SCNR. ;-)

I set the custom file myself and I found the "phrase" there.  It's
longish and hard to type.  Distributors somethimes have different
plans--for SuSE Linux 8.2 I'll add some note to the manual...

> But, IIRC, it should never be necessary to type it for canceling or
> superseding messages.

In theory ;)  I'll dare an update next time--maybe, the problem is
already fixed.

> After updating, you'll find more info in <info://message/Canceling+News>.

Thanks again!

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Superseding trick not working

[Simon Josefsson]

Karl Eichwalder <keichwa@gmx.net> writes:

> At the moment, I'm not able to supersede an article:
>
> First, I tried the trick described in the manual:
>
>        If you have just posted the article, and change your mind right away,
>     there is a trick you can use to cancel/supersede the article without
>     waiting for the article to appear on your site first.  You simply return
>     to the post buffer (which is called `*sent ...*').  There you will find
>     the article you just posted, with all the headers intact.  Change the
>     `Message-ID' header to a `Cancel' or `Supersedes' header by
>     substituting one of those words for the word `Message-ID'.  Then just
>     press `C-c C-c' to send the article as you would do normally.  The
>     previous article will be canceled/superseded.
>
> But Gnus complains:
>
> Debugger entered--Lisp error: (error "Denied posting -- multiple copies")
>   signal(error ("Denied posting -- multiple copies"))
>   error("Denied posting -- multiple copies")
>   message-send(nil)
>   message-send-and-exit(nil)
>   call-interactively(message-send-and-exit)

This looks like a GNKSA feature.  The code indicates that

(add-to-list 'message-shoot-gnksa-feet 'multiple-copies)

would remove the error message.  The manual probably should be
updated, or the code changed to not use this GNKSA feature when a
Cancel/Supersede header is present.

> Going the old `S s' way, Gnus wants to know a "Canlock" thingie?
> What's that?  I've never setup such a password.

Gnus should create and store such a "password" automatically and put
it in your ~/.emacs, doesn't it?

Fixing whatever bugs in the cancel/supersede seems important IMHO,
since if there are bugs in that code people will (rightly) get the
feeling that Cancel Locks are a bad idea since it interfer with how
they work.

Re: Superseding trick not working

[Karl Eichwalder]

Simon Josefsson <jas@extundo.com> writes:

> This looks like a GNKSA feature.  The code indicates that
>
> (add-to-list 'message-shoot-gnksa-feet 'multiple-copies)
>
> would remove the error message.  The manual probably should be
> updated, or the code changed to not use this GNKSA feature when a
> Cancel/Supersede header is present.

Sounds reasonable; thanks for the info.

> Gnus should create and store such a "password" automatically and put
> it in your ~/.emacs, doesn't it?

Okay, it did.  But it's in (custom-set-variables ...) -- the question
is whether Gnus is allowed to touch this form.  I vote to write the
password to say ~/.gnus-canlock-password and read it from there.  I'm I
allowed to change it to something I'm able to remember like "emacs"? ;)

> Fixing whatever bugs in the cancel/supersede seems important IMHO,
> since if there are bugs in that code people will (rightly) get the
> feeling that Cancel Locks are a bad idea since it interfer with how
> they work.

Thanks for your commitment!

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Superseding trick not working

[Simon Josefsson]

Karl Eichwalder <keichwa@gmx.net> writes:

>> Gnus should create and store such a "password" automatically and put
>> it in your ~/.emacs, doesn't it?
>
> Okay, it did.  But it's in (custom-set-variables ...) -- the question
> is whether Gnus is allowed to touch this form.  I vote to write the
> password to say ~/.gnus-canlock-password and read it from there.

Gnus uses `customize-save-variable'.  The problem with
~/.gnus-canlock-password is that we'll have yet another ~/.newsrc.eld
file that we must document and be backwards compatible with.  IMHO it
seems better to use an API for handling that, and all the boring stuff
can be hidden inside custom, and documented in one place.  Maybe it is
a good idea to hear what the Emacs gurus feel.

> I'm I allowed to change it to something I'm able to remember like
> "emacs"? ;)

Yup.  Since no servers use it yet, it doesn't even have to be secret
just as long as you remember it.

Re: Superseding trick not working

[Lars Magne Ingebrigtsen]

Karl Eichwalder <keichwa@gmx.net> writes:

> Debugger entered--Lisp error: (error "Denied posting -- multiple copies")
>   signal(error ("Denied posting -- multiple copies"))

Yup.  Fix in Oort Gnus v0.13 (i. e., CVS).

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen