nndrafts squawk

nndrafts squawk

[Harry Putnam]

Its irritated me enough again to make me squawk some more.
The new behavior of nndrafts.  By new I mean a couple mnths I think.

I keep finding things in drafts that I've already sent.  It might be
an unfinished version or sometimes the whole thing.  If I kill a
composition after its been setting  a while, it ends up in drafts.

This is wrong wrong wrong, to my way of thinking, and definitely a big
change from the old behavior. 

No one else seems bothered by it.  The worst thing I see with this, is
finding a message a day or so later and then not being sure if it was
sent or not.  Confusing and unecessary.

I want only C-c C-d to go to drafts and stay there.  Absolutely
nothing else.  No crashes no kills no baloney at all.  Any thing
killed should vanish right then and there.  I'd much prefer losing a
carefully created composition once a year than keep finding confusing
remnants or already sent stuff, or killed stuff in there.

Now how can I get that kind of behavior on my setup?  Is there
something I can tweak, jiggle, twist or slap, to stop this behavior?