From: Bud Rogers <budr@sirinet.net>
Cc: ding@gnus.org
Subject: Re: oooohhhhh... bitten once again by an evil "reply-to"-setting mailing list
Date: 13 Aug 1998 10:45:57 -0500 [thread overview]
Message-ID: <m24svganre.fsf@twocups.sirinet.net> (raw)
In-Reply-To: Randal Schwartz's message of "13 Aug 1998 08:20:24 -0700"
Edit Group Properties for the offending lists. I stumbled onto this while
wandering around in the gnus info files.
`broken-reply-to'
Elements like `(broken-reply-to . t)' signals that `Reply-To'
headers in this group are to be ignored. 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. This is
broken behavior. So there!
--
Bud Rogers <budr@sirinet.net>
formerly <budr@tanet.net>
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
1998-08-13 15:45 ` Bud Rogers [this message]
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=m24svganre.fsf@twocups.sirinet.net \
--to=budr@sirinet.net \
--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).