From: Leo <sdl.web@gmail.com>
To: ding@gnus.org
Subject: gnus-delay-article and attachment
Date: Wed, 11 May 2011 13:57:43 +0800 [thread overview]
Message-ID: <m1oc3922zs.fsf@th041100.ip.tsinghua.edu.cn> (raw)
Hello all,
If I queue up a bunch of (well-prepared) emails to send in future (eg.
3days). At the time the messages are sent, attachments (e.g. from a file
or buffer) may not exist anymore. How to get rid of this annoyance?
Leo
next reply other threads:[~2011-05-11 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 5:57 Leo [this message]
2011-05-11 21:45 ` Ted Zlatanov
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=m1oc3922zs.fsf@th041100.ip.tsinghua.edu.cn \
--to=sdl.web@gmail.com \
--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).