From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Mail digest and MIME headers
Date: 06 Feb 2001 09:09:18 -0500 [thread overview]
Message-ID: <2nu267dhtd.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <rjn1c0vu1b.fsf@ssv2.dina.kvl.dk> (Per Abrahamsen's message of "06 Feb 2001 14:08:00 +0100")
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Why does "gnus-uu-digest-mail-forward" insert
>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
>
> in each digested message? This is the default content type, so there
> should be no reason to insert the headers.
Fixed.
ShengHuo
--
(setq gnus-posting-styles '((".*" (signature-file "~/.signature"))))
next prev parent reply other threads:[~2001-02-06 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 13:08 Per Abrahamsen
2001-02-06 14:09 ` ShengHuo ZHU [this message]
2001-02-06 22:41 ` Per Abrahamsen
2001-02-06 22:53 ` Russ Allbery
2001-02-06 23:04 ` Per Abrahamsen
2001-02-07 0:45 ` Russ Allbery
2001-02-06 23:09 ` ShengHuo ZHU
2001-02-06 23:16 ` Per Abrahamsen
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=2nu267dhtd.fsf@tiger.jia.vnet \
--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).