From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: oooohhhhh... bitten once again by an evil "reply-to"-setting mailing list
Date: 13 Aug 1998 17:45:44 +0200 [thread overview]
Message-ID: <vafk94c7umv.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Randal Schwartz's message of "13 Aug 1998 08:20:24 -0700"
>>>>> Randal Schwartz <merlyn@stonehenge.com> writes:
> OK, what can I do about those lame mailing lists (about a fourth
> of them, in my experience) that add "reply-to:
> the-list@where.ever", so that both the "r" and the "f" buttons do
> EXACTLY the SAME THING?
There's a `broken reply-to' group parameter. Type G c on the group.
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next prev parent reply other threads:[~1998-08-13 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-13 15:20 Randal Schwartz
1998-08-13 15:45 ` Kai Grossjohann [this message]
1998-08-13 15:45 ` Bud Rogers
1998-08-13 15:53 ` Randal Schwartz
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=vafk94c7umv.fsf@ramses.cs.uni-dortmund.de \
--to=grossjohann@amaunet.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).