From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: Header dependant headers?
Date: 13 Mar 1998 15:21:47 -0800 [thread overview]
Message-ID: <r9qk99ygos4.fsf@torigai.cs.washington.edu> (raw)
In-Reply-To: Edvard Majakari's message of "13 Mar 1998 14:44:26 +0200"
I'm sure there's some hook you can use for this, but gnus already
includes a nice mechanism for handling followups & postings to mailing
lists.
All you have to do is to split each list into a separate group; then
just add this group parameter:
(to-address . "ding@gnus.org")
It also works for groups you read via NNTP but are gatewayed from an
email list and you want to followup to the email list (SMTP) instead
of the newsgroup (NNTP).
--Paul
>>>>> Edvard Majakari writes:
> Feature suggestion. The Ultimate Tool(TM) in Gnus? If a mail message
> contains some header (rexexp), it inserts/changes some headers in
> reply. Main reason for this is that when some people send me mail via
> cc: header, they fail to include reply-to header pointing to the
> list.. what I was thinking was something like
> (gnus-magic-header-include
> ("rexexp_matching_some_header" "foo")
> )
> Which would include header foo to reply or change header to foo if it
> already existed. Like, suppose you'd want to include header Reply-to:
> foo@baf.org to any mails pointed to ding.* mailing lists when
> replying. You'd say something like
> (gnus-magic-header-include
> ("To: ding@.*" "Reply-To: foo@baf.org")
> )
next prev parent reply other threads:[~1998-03-13 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-13 12:44 Edvard Majakari
1998-03-13 23:21 ` Paul Franklin [this message]
1998-03-16 12:16 ` Edvard Majakari
1998-03-21 19:21 ` Hans de Graaff
1998-03-23 13:23 ` 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=r9qk99ygos4.fsf@torigai.cs.washington.edu \
--to=paul@cs.washington.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).