From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: What hook to use for headercleaning?
Date: Fri, 13 Jun 2003 11:12:56 +0200 [thread overview]
Message-ID: <yoijsmqe1gtj.fsf@helm.dd.chalmers.se> (raw)
In-Reply-To: <xpxyr85ycpy5.fsf@Germany.Sun.com>
Peter.Weiss@germany.sun.com (Peter Weiss, Sun Microsystems, Germany) writes:
> I'm subscribed on some mailing lists that set the "Reply-To:" field
> to the list :-( Ugly, ugly...
>
> What's the best way to clean this using gnus?
(info "(gnus)Group Parameters")
`broken-reply-to'
Elements like `(broken-reply-to . t)' signals that `Reply-To'
headers in this group are to be ignored, and for the header to be
hidden if `reply-to' is part of `gnus-boring-article-headers'.
This can be useful if you're reading a mailing list group where
the listserv has inserted `Reply-To' headers that point back to
the listserv itself. That is broken behavior. So there!
--
The day Microsoft makes something that doesn't suck is probably the
day they start making vacuum cleaners. -- Ernst Jan Plugge
next prev parent reply other threads:[~2003-06-13 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 9:00 Peter Weiss, Sun Microsystems, Germany
2003-06-13 9:12 ` Johan Bockgård [this message]
2003-06-13 13:27 ` Peter Weiss, Sun Microsystems, Germany
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=yoijsmqe1gtj.fsf@helm.dd.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
/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).