Make nndrafts quit being overly helpful

[Harry Putnam <reader@newsguy.com>]

A couple of months or so ago there were some changes made to nndrafts
that causes a behavior that is irritating, but more over I think it is
wrong behavior as well.

For several years now I've been using a technique to edit and save
messages or several messages by using either `e' or in the case of a
thread I might use S O m (gnus-uu-digest-mail-forward) to first create
a sort of digest.  Then edit the whole thing.

I have a home made function I then invoke that sends the edited
message where ever I want it on my groups.  I then kill the edit
buffer. My function is hooked into all edit modes so I can invoke
it in any composition or edit buffer.

For some time now, if the editing lasts long enough for auto save to
happen then the killed buffer (`S O m' `F' `R' but not `e') reappears
in nndrafts.

This can also happen if you start a composition then decide to trash
it. It might show up in nndrafts causing confusion as to what the game
plan was.

A purposely killed buffer should *NOT* reappear in nndrafts.  No
killed or otherwise crashed, demised, curtailed or eschewed buffer
should.

Only drafts from either C-x C-s or preferable C-x C-d should go
there.  Nothing else.  After all it is a `drafts' group.  Not a
recovery, crash, recycle, second chance, data recovery group.
Or AA clinic. :-)
 
Maybe it is difficult to tell the difference between a willfully
killed and crashed buffer, but in fact neither should be going to
drafts.

Do we need an nnrecover  or nnMSrecyle_bin...?  Seriously, that may be
a good thing to have.  But it should not be drafts.

Can I do something locally to control this?  I mean, short of major
coding.