From: Glyn Millington <wistanswick@linuxmail.org>
Subject: Re: message-default-headers
Date: Thu, 29 Sep 2005 03:30:14 +0100 [thread overview]
Message-ID: <87k6h04nd5.fsf@nowhere.org> (raw)
In-Reply-To: <m3achwtz4y.fsf@prod01.jerrysievers.com>
Jerry Sievers <jerry@jerrysievers.com> writes:
> Hello;
>
> I am trying to get a few custom headers into mail message buffers from
> Gnus and thought I could set the message-default-headers variable in
> the group parameters to make it work.
>
> ((total-expire . t)
> (message-default-headers "Test-Header: foo"))
>
> Doesn't work though.
>
> Tried making the message-default-headers variable buffer local and
> also tried setting message-generate-headers-first to 't' to no avail.
NB I am NOT an expert!!
Group parameters are dotted pairs, so should it be
(message-default-headers . "Test-Header: foo") ??
However, in the manual "message-default-headers" is not listed as an
acceptable group parameter. So maybe you could do it via the
posting-style parameter which IS listed
> From manual section 2.10
,----
| posting-style
|
| You can store additional posting style information for this group here
| (see section 5.5 Posting Styles). The format is that of an entry in
| the gnus-posting-styles alist, except that there's no regexp matching
| the group name (of course). Style elements in this group parameter
| will take precedence over the ones found in gnus-posting-styles.
|
| For instance, if you want a funky name and signature in this group
| only, instead of hacking gnus-posting-styles, you could put something
| like this in the group parameters:
|
|
|
| (posting-style
| (name "Funky Name")
| ("X-My-Header" "Funky Value")
| (signature "Funky Signature"))
`----
Funky, eh?
hth
Glyn
next prev parent reply other threads:[~2005-09-29 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 1:56 message-default-headers Jerry Sievers
2005-09-29 2:30 ` Glyn Millington [this message]
2005-09-29 2:44 ` message-default-headers Glyn Millington
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=87k6h04nd5.fsf@nowhere.org \
--to=wistanswick@linuxmail.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).