From: Allan <mu8ja0i@earthlink.net>
To: info-gnus-english@gnu.org
Subject: Re: Automatically insert X-No-Archive in headers
Date: Sat, 29 Dec 2007 21:10:00 -0600 [thread overview]
Message-ID: <u7iiw6fp3.fsf@earthlink.net> (raw)
In-Reply-To: <cs9odc96ij4.fsf@Psilocybe.Update.UU.SE>
Andreas Davour <anteRUN@updateLIKE.uu.HELLse> writes:
> Is there a way to insert the no-archive header automatically, so I don't
> have to type C-c C-f a all the time?
>
> I've not found any indication in the manual, but am a bit new at serious
> gnus usage anyway.
>
> /Andreas
>
> --
> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
Message default headers (message-required-news-headers) are covered in the Gnus manual but I will simply share with you my .gnus init file which you can adapt to your own purpose easily enough. Just change the string "Reply-to" to "X-No-Archive" and fill in the desired non-nil value since I don't remember the syntax of that header. If you set it to `t' the header will be added. You may also want to check the value of gnus-init-file. Mine is called "_gnus" for Windows compatibility reasons. After you get it working you can byte-compile it for efficiency to create ".gnus.elc" . If you want more headers later on simply add them as additional arguments to the `(list )' construct on line one of the code in the same form '(optional. x)`.
;; `_gnus.el' : this runs when gnus starts
;;
;; add a "reply-to" header to optional news message headers
(setq-default message-required-news-headers (append message-required-news-headers (list `(optional . Reply-to))))
;; set the message Reply-to to the message default reply-to
(setq-default Reply-to `"whatever_value_you_want")
next prev parent reply other threads:[~2007-12-30 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 2:08 Andreas Davour
2007-12-30 3:10 ` Allan [this message]
2007-12-30 18:01 ` Andreas Davour
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=u7iiw6fp3.fsf@earthlink.net \
--to=mu8ja0i@earthlink.net \
--cc=info-gnus-english@gnu.org \
--cc=noreply@accessdenied.xxx \
/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).