From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: GNUS mailing list <ding@gnus.org>
Subject: Re: complete mail headers in gnus-user-format-function?
Date: Fri, 12 May 2000 19:33:09 +0200 (MET DST) [thread overview]
Message-ID: <200005121733.TAA12951@marcy.cs.uni-dortmund.de> (raw)
In-Reply-To: Pavel.Janik@inet.cz's message of "Fri, 12 May 2000 15:41:24 +0200"
Pavel.Janik@inet.cz (Pavel Janík ml.) writes:
> I added the header to the extra-headers so it is then passed in
> (mail-header-extra gnus-tmp-header). But this is not what I want...
I'm not sure what happens for all backends. Hm. But the nnml summary
is generated only from the info that's in the .overview file. So you
have to add the header to nnmail-extra-headers. I don't know how
backends without overview files deal with this.
Or am I mistaken?
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-05-12 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-12 13:41 Pavel Janík ml.
2000-05-12 17:33 ` Kai Großjohann [this message]
2000-08-13 16:56 ` Lars Magne Ingebrigtsen
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=200005121733.TAA12951@marcy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).