From: steve@miranova.com (Steven L. Baur)
Cc: Sudish Joseph <joseph@cis.ohio-state.edu>
Subject: Re: About to-addresses and followup [poll]
Date: 13 Nov 1995 23:20:59 -0800 [thread overview]
Message-ID: <m2g2fr64ro.fsf@diana.miranova.com> (raw)
In-Reply-To: Sudish Joseph's message of 13 Nov 1995 20:43:39 -0800
>>>>> "Sudish" == Sudish Joseph <joseph@cis.ohio-state.edu> writes:
Sudish> PS: GNUS didn't insert a References: header on your reply,
Sudish> could you see why?
Let me answer the somewhat obscure question first. I traced it as far
as tm. Once I turn off Mime, the References are inserted (as they are
in this followup).
Speaking of bugs, here's another variant of the headers on followup:
To: ding@ifi.uio.no
CC: (Steven L. Baur), The Ding List <ding@ifi.uio.no>
Steve> (I question the rationale for the practice of Cc'ing by
Steve> default to the author on followup to a mailing list)
Sudish> For lots of mailing lists, it is common that the person
Sudish> who originated the thread is not a member of the list.
I thought this was considered bad etiquette in general. But if that
has changed, that's O.K.
Sudish> For e.g., lists related to software--a person asks a
Sudish> question but isn't interested in other topics being
Sudish> discussed. If we discard CC'ed addresses, this person
Sudish> will lose all second and higher level messages in the
Sudish> ensuing discussion. If we don't respect even the To:
Sudish> header, people will get no replies whatsoever. I pray we
Sudish> don't try to enforce such a model.
O.K. It's enough for me to know there are passionate supporters for
this feature. Be conservative in what you send, liberal in what you
accept ...
Sudish> Duplicate elimination is a simple process with most
Sudish> filters.
And the simplest approach (as with procmail) has its drawbacks. What
confuses me greatly is mistaking the private copy of the public
version (either to a mailing list or on Usenet), as private e-mail.
I'll get over it.
Steve> How will gnus-auto-mail-to-author relate?
Sudish> It doesn't enter the picture for mailgroups.
Why shouldn't it? Besides, if you base the behavior on a variable,
won't it be easier to get variant behavior out of the (local)
variables of the Score file, or off the group hook?
Regards,
--
steve@miranova.com baur
next prev parent reply other threads:[~1995-11-14 7:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-14 0:56 Steven L. Baur
1995-11-14 4:43 ` Sudish Joseph
1995-11-14 7:20 ` Steven L. Baur [this message]
1995-11-14 8:17 ` Sudish Joseph
1995-11-14 13:00 ` Per Abrahamsen
1995-11-15 2:58 ` Steven L. Baur
1995-11-15 3:41 ` Sudish Joseph
1995-11-18 6:49 ` Lars Magne Ingebrigtsen
1995-11-18 8:14 ` Steven L. Baur
1995-11-19 7:43 ` Lars Magne Ingebrigtsen
1995-11-18 16:40 ` Per Abrahamsen
1995-11-19 7:43 ` Lars Magne Ingebrigtsen
1995-11-22 0:27 ` Felix Lee
1995-11-23 12:36 ` Lars Magne Ingebrigtsen
1995-11-23 22:55 ` Sudish Joseph
1995-11-26 14:22 ` Lars Magne Ingebrigtsen
1995-11-14 15:53 ` Sten Drescher
1995-11-15 4:08 ` Sudish Joseph
-- strict thread matches above, loose matches on Subject: below --
1995-11-13 22:51 Sudish Joseph
1995-11-13 23:49 ` Per Abrahamsen
1995-11-14 0:07 ` Sudish Joseph
1995-11-14 1:17 ` Per Abrahamsen
1995-11-14 4:55 ` Sudish Joseph
1995-11-14 12:40 ` Per Abrahamsen
1995-11-15 3:53 ` Sudish Joseph
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=m2g2fr64ro.fsf@diana.miranova.com \
--to=steve@miranova.com \
--cc=joseph@cis.ohio-state.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).