Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
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 16:26:40 +0200	[thread overview]
Message-ID: <1282227742-sup-874@eris> (raw)
In-Reply-To: <1282222218-sup-5975@tilus.net>

Excerpts from Tero Tilus's message of 2010-08-19 15:07:37 +0200:
> Philipp Überbacher, 2010-08-19 15:40:
> > I'd like it the other way around, always reply to list and simply
> > change to 'sender' in the (at least for me) rare cases where it's
> > not supposed to go to the list.
> 
> It is reasonable that replying to list mail defaults to "Mailing list"
> as reply mode.
> 
> Sup does pretty good job being list aware.  I think the problem here
> is sup failing to detect a list mail and treating it as "ordinary"
> mail.  There are at least two cases when sup could (afaik) miss a list mail.

Yep, sup is definitely doing a good job, it seems to be sane in almost
any case.

> 1) A mail which is sent to/cc/bcc a list member and the list so that
> list member gets two copies of the mail.  Sup "sees" only the first
> one to arrive, which most probably is the non-list duplicate.
> 
> 2) A similar mail than previous but the copy via list is not delivered
> at all.  Maybe the list performs delivery magic ("whoa, cc-header
> shows that this list member already got the mail) or whatelse.

I just checked my most active lists and they all were set to 'avoid
duplicates if your address is in CC or TO'. I changed that and will see
what happens. Maybe sup is clever enough to discard the non-list message.

> You can enumerate mailing lists to mutt and have it consider mails
> to/cc a such address as list mails regardless of the precence of list
> headers.

I don't know anything about mutt and don't consider using it. I'm fairly
happy with sup :)
-- 
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

  parent reply	other threads:[~2010-08-19 14:26 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 [this message]
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
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=1282227742-sup-874@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