From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: archiving sans attachments
Date: Tue, 3 Oct 2000 08:49:10 -0400 [thread overview]
Message-ID: <200010031249.e93CnAE05403@zsh.2y.net> (raw)
In-Reply-To: <i5klmw6jewb.Thalia@gromit.ph.surrey.ac.uk>
Paul Stevenson <p.stevenson@surrey.ac.uk> writes:
> Hello,
> Is it possible for messages which were sent with attachments to be
> archived without the attachment (but perhaps the MML code so one knows
> what was going on?). At the moment I'm just using Gcc: to an
> appropriate nnfolder.
Gnus doesn't has such a feature. But the following code could do that.
(require 'gnus-msg)
(defadvice gnus-inews-do-gcc
(around gnus-news-do-gcc-inhibit-body-encoding first activate)
(let ((message-inhibit-body-encoding t))
ad-do-it))
I'd like to know whether it works for you.
ShengHuo
next prev parent reply other threads:[~2000-10-03 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 12:19 Paul Stevenson
2000-10-03 12:49 ` ShengHuo ZHU [this message]
2000-10-03 12:54 ` Paul Stevenson
2000-10-03 13:03 ` ShengHuo ZHU
2000-10-03 13:10 ` Paul Stevenson
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=200010031249.e93CnAE05403@zsh.2y.net \
--to=zsh@cs.rochester.edu \
/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).