From: jidanni@jidanni.org
To: ding@gnus.org
Subject: Drafts' attachments will go bye-bye
Date: Tue, 18 Mar 2008 10:23:22 +0800 [thread overview]
Message-ID: <20080318022322.GA13333@jidanni.org> (raw)
How is employee Holmes going to face his boss when he comes into work
next week, boots his computer, and realizes the attachment he thought
was safe and sound inside Gnus' Drafts folder was merely a pointer to
a place now long gone!
$ cat News/drafts/drafts/1
From: Holmes
To: the_boss
Subject: important attachment
--text follows this line--
Dear Boss, attached is the important attachment.
<#part type="application/x-cpio" filename="/tmp/important.cpio"disposition=attachment>
<#/part>
OK, Gcc: indeed saves the attachment, not just the pointer, so what's
the justification for not doing the same in the Drafts state? Anyway,
at least document this danger somewhere in the Message or Gnus Info trees.
Go ahead and do the same experiment with mutt. Type a to attach a
file, and q to postpone your message. Then next week look in ~/postponed.
Yup, still there safe and sound is your attachment, vs. the "even my
car keys and shoes were gone" gnus' broken pointer.
reply other threads:[~2008-03-18 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080318022322.GA13333@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.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).