From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnus accumulating copies of a draft when sending is not possible
Date: Sun, 24 Oct 2021 16:53:30 +0200 [thread overview]
Message-ID: <87fssqtqxh.fsf@web.de> (raw)
In-Reply-To: 87pmru8rw7.fsf@gnus.org
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Are there duplicated drafts on disk in the drafts directory?
Yes. Today they are numbered 1, 3, 5, ...
They are not absolutely identical for me. 1, the only one I saved
explicitly without trying to send before, has no Message-ID and Date and
these fields.
The files 3, 5, ... have these fields, and these fields differ.
I also found that each duplicate seems to start as an auto-save-file,
e.g. #3#. But it gets picked up by Gnus, it gets listed as draft, and
after each failed send attempt, #3# has become 3, and I have another
#5#, and so on. Didn't investigate what causes the auto-save files to
become a file which isn't named #*#.
Michael.
next prev parent reply other threads:[~2021-10-24 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 21:00 Gnus accumulating copies of a draft when sending is not possible H. Dieter Wilhelm
2021-10-20 8:14 ` Lars Ingebrigtsen
2021-10-20 20:21 ` H. Dieter Wilhelm
2021-10-21 13:14 ` Lars Ingebrigtsen
2021-10-22 6:42 ` H. Dieter Wilhelm
2021-10-22 7:02 ` Eric S Fraga
2021-10-22 7:50 ` Michael Heerdegen
2021-10-22 21:04 ` H. Dieter Wilhelm
2021-10-23 8:07 ` Michael Heerdegen
2021-10-28 6:34 ` H. Dieter Wilhelm
2021-10-28 10:03 ` Michael Heerdegen
2021-10-22 16:54 ` Lars Ingebrigtsen
2021-10-23 8:16 ` Michael Heerdegen
2021-10-23 16:10 ` Eric Abrahamsen
2021-10-24 7:54 ` Michael Heerdegen
2021-10-24 13:38 ` Lars Ingebrigtsen
2021-10-24 14:53 ` Michael Heerdegen [this message]
2021-10-24 15:17 ` Michael Heerdegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fssqtqxh.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).