From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs51253bki; Thu, 19 Aug 2010 13:30:53 -0700 (PDT) Received: by 10.224.11.141 with SMTP id t13mr244951qat.307.1282249852406; Thu, 19 Aug 2010 13:30:52 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t26si3813360qco.79.2010.08.19.13.30.51; Thu, 19 Aug 2010 13:30:52 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BB8D419783CD; Thu, 19 Aug 2010 16:30:51 -0400 (EDT) X-Greylist: delayed 401 seconds by postgrey-1.31 at rubyforge.org; Thu, 19 Aug 2010 16:18:15 EDT Received: from talbot.seas.upenn.edu (talbot.seas.upenn.edu [158.130.67.217]) by rubyforge.org (Postfix) with ESMTP id 2FA0F185836B for ; Thu, 19 Aug 2010 16:18:15 -0400 (EDT) Received: from understudy.seas.upenn.edu (understudy.seas.upenn.edu [158.130.67.161]) by talbot.seas.upenn.edu (8.14.3/8.14.3) with ESMTP id o7JKBRD2032243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 19 Aug 2010 16:11:27 -0400 Received: from understudy.seas.upenn.edu (LOCALHOST.upenn.edu [127.0.0.1]) by understudy.seas.upenn.edu (8.13.6/8.13.6) with ESMTP id o7JKBP06003370 for ; Thu, 19 Aug 2010 16:11:25 -0400 Received: (from wwwrun@localhost) by understudy.seas.upenn.edu (8.13.6/8.13.1/Submit) id o7JKBP2Q003369 for sup-talk@rubyforge.org; Thu, 19 Aug 2010 16:11:25 -0400 X-Authentication-Warning: understudy.seas.upenn.edu: wwwrun set sender to wagnerdm@seas.upenn.edu using -f Message-ID: <20100819161125.19162nsavhg7u5tc@webmail.seas.upenn.edu> X-Source-IP: 71.175.249.160 X-Authenticated-User: wagnerdm Date: Thu, 19 Aug 2010 16:11:25 -0400 From: wagnerdm@seas.upenn.edu To: sup-talk@rubyforge.org References: <1282214690-sup-777@eris> <1282218941-sup-4503@duck> <1282220819-sup-9512@theshire> <1282221544-sup-9759@eris> <1282222218-sup-5975@tilus.net> <1282227742-sup-874@eris> <1282241633-sup-6722@tilus.net> In-Reply-To: <1282241633-sup-6722@tilus.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.4) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.0.10011, 1.0.148, 0.0.0000 definitions=2010-08-19_09:2010-08-19, 2010-08-19, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-1005130000 definitions=main-1008190162 Subject: Re: [sup-talk] mailinglists in CC X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="Yes" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Sort of an edge-case, but what would this mean for cross-posted = messages, i.e., messages sent to multiple mailing lists? ~d Quoting Tero Tilus : > Philipp =DCberbacher, 2010-08-19 17:26: >>> 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 :) > > I wasn't suggesting you to go mutt yourself. ;) I was just wondering > how other mailclients have resolved this problem of duplicate replies > (one list and one off-list) from ill-behaving mailclients. > > Possible solution would be to maintain list of known mailinglist > addresses (say mailinglists.txt, just like we now have labels.txt) and > consider all mails targeted to a list address as list mail even if > they wouldn't have list headers. > > Any considerations on the implications that would have? > > -- > Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk