From: "Philipp Überbacher" <hollunder@lavabit.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mailinglists in CC
Date: Thu, 19 Aug 2010 14:58:38 +0200 [thread overview]
Message-ID: <1282222230-sup-4129@eris> (raw)
In-Reply-To: <1282220267-sup-5326@tilus.net>
Excerpts from Tero Tilus's message of 2010-08-19 14:33:24 +0200:
> Philipp, 2010-08-19 13:52:
> > Some clients seem to put the mailinglist in the CC field.
>
> Which is pretty annoying.
Yes, but the chance of having everyone else change that is pretty slim.
> > Apparently if someone with such a client replies to me, sup will
> > automatically reply to the person, not to the list.
>
> This might (and I really am guessing here) be because sup skips
> duplicates (by message id). In the first exaple you get the mail
> twice (assuming you are subscribed to lista). The one you most
> probably get first (and gets indexed first) is the message you get
> directly and which does not have list headers. The one which makes
> the extra hop via list server (and has the list headers) gets to you
> later and is simply discarded as duplicate. When you go reply the
> mail, sup is perfectly unaware of it being a list mail.
That makes sense. Could it check for the presence of list headers and
discard the one without?
One thing I noticed with the list in CC mails is that replying to
'recipient' would reply to the list. I don't get that from a semantic
point.
> > It's really annoying to send to single people instead of the list by
> > accident.
>
> I can tell you it is _way_ more annoying to accidentally send private
> mail to list (I've done that, once _really_ badly). So this behavior
> (automatical selection between list reply and private reply) should
> IMO be conservative in this sense.
I see your point. I don't know what conservative behavior would be in
this case. I think consistency is key though.
--
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-08-19 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 10:52 Philipp
2010-08-19 11:58 ` Israel Herraiz
2010-08-19 12:27 ` Erin Sheldon
2010-08-19 12:40 ` Philipp Überbacher
2010-08-19 13:07 ` Tero Tilus
2010-08-19 13:21 ` Helge Titlestad
2010-08-19 18:31 ` Tero Tilus
2010-08-19 14:26 ` Philipp Überbacher
2010-08-19 18:24 ` Tero Tilus
2010-08-19 19:19 ` Philipp Überbacher
2010-08-19 20:11 ` wagnerdm
2010-08-19 12:29 ` Philipp Überbacher
2010-08-19 12:49 ` Tero Tilus
2010-08-19 13:39 ` Israel Herraiz
2010-08-19 12:33 ` Tero Tilus
2010-08-19 12:58 ` Philipp Überbacher [this message]
2010-08-19 13:41 ` Israel Herraiz
2010-08-19 14:10 ` Philipp Überbacher
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=1282222230-sup-4129@eris \
--to=hollunder@lavabit.com \
--cc=sup-talk@rubyforge.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