From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: info-gnus-english@gnu.org, Felix Natter <fnatter@gmx.net>
Subject: Expiring sent drafts does now always `delete'
Date: Thu, 28 Mar 2013 10:36:29 +0900 [thread overview]
Message-ID: <b4my5d82tlu.fsf_-_@jpl.org> (raw)
In-Reply-To: <mailman.22943.1364408991.855.info-gnus-english@gnu.org>
Hi,
This might be a regression but I think it would trouble no one.
I made draft messages come to be deleted after being sent regardless
of the value of `nnmail-expiry-target'. If it is `delete', that
is the default, the behavior is unchanged. Before this change,
a sent draft was moved to an expiry group if `nnmail-expiry-target'
specifies it. However, there were some problems with moved drafts:
1. A separator is left between the header and the body. It causes
the body of a moved draft to be unable to read.
Even if one sets or binds `mail-header-separator' to "",
2. A message is in MML, not MIME. I.e., non-ASCII text is as is,
attachments are mere tags.
3. There seems to be an unresolved bug.
See also:
http://article.gmane.org/gmane.emacs.gnus.user/16110
http://article.gmane.org/gmane.emacs.gnus.user/16114
http://article.gmane.org/gmane.emacs.gnus.user/16160
http://article.gmane.org/gmane.emacs.gnus.user/16163
http://article.gmane.org/gmane.emacs.gnus.user/16164
http://article.gmane.org/gmane.emacs.gnus.user/16165
http://article.gmane.org/gmane.emacs.gnus.user/16166
(The thread is broken because info-gnus-english@gnu.org rewites
Message-IDs. :<)
There are similar problems with draft messages that are copied
or moved to normal groups by `B c' or `B m'. But IMHO, it's not
worth improving, since you can use Gcc or something if you want
to archive sent messages.
Regards,
next prev parent reply other threads:[~2013-03-28 1:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19525.1360518618.855.info-gnus-english@gnu.org>
2013-02-13 0:18 ` Sent message still in drafts (lisp error: "Selecting deleted buffer") Katsumi Yamaoka
2013-03-25 20:41 ` Felix Natter
[not found] ` <mailman.22829.1364244138.855.info-gnus-english@gnu.org>
2013-03-26 1:50 ` Katsumi Yamaoka
2013-03-26 19:58 ` Felix Natter
[not found] ` <mailman.22889.1364327929.855.info-gnus-english@gnu.org>
2013-03-27 0:17 ` Katsumi Yamaoka
2013-03-27 18:29 ` Felix Natter
[not found] ` <mailman.22943.1364408991.855.info-gnus-english@gnu.org>
2013-03-28 1:36 ` Katsumi Yamaoka [this message]
2013-03-31 18:19 ` Felix Natter
2013-03-31 23:48 ` Katsumi Yamaoka
2013-03-31 23:59 ` Katsumi Yamaoka
2013-04-01 7:31 ` Felix Natter
[not found] ` <mailman.23203.1364801493.855.info-gnus-english@gnu.org>
2013-04-01 9:44 ` Katsumi Yamaoka
2013-04-01 12:20 ` Felix Natter
[not found] ` <mailman.23213.1364818828.855.info-gnus-english@gnu.org>
2013-04-02 1:40 ` Katsumi Yamaoka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4my5d82tlu.fsf_-_@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=fnatter@gmx.net \
--cc=info-gnus-english@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 NNTP newsgroup(s).