From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs45098bki; Thu, 19 Aug 2010 11:31:59 -0700 (PDT) Received: by 10.229.52.28 with SMTP id f28mr71543qcg.241.1282242717420; Thu, 19 Aug 2010 11:31:57 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t31si3558545qcs.168.2010.08.19.11.31.56; Thu, 19 Aug 2010 11:31:57 -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 CA3BE1858381; Thu, 19 Aug 2010 14:31:56 -0400 (EDT) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 206001858374 for ; Thu, 19 Aug 2010 14:31:40 -0400 (EDT) Received: by kuovi.tilus.net (Postfix, from userid 1000) id A329A1EF1E; Thu, 19 Aug 2010 21:31:40 +0300 (EEST) From: Tero Tilus To: sup-talk In-reply-to: <1282223762-sup-1786@colargol.tihlde.org> References: <1282214690-sup-777@eris> <1282218941-sup-4503@duck> <1282220819-sup-9512@theshire> <1282221544-sup-9759@eris> <1282222218-sup-5975@tilus.net> <1282223762-sup-1786@colargol.tihlde.org> Date: Thu, 19 Aug 2010 21:31:40 +0300 Message-Id: <1282242449-sup-1456@tilus.net> User-Agent: Sup/git 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Helge Titlestad, 2010-08-19 16:21: > If sup is doing the removal of duplicates, could we get sup to > update the List-* headers if there are any new ones? That would help with the off-list dupe getting indexed first, but not with the (pretty common) mailinglist setup where the list server plays clever and skips delivery to mailinglist members already appearing in recipient list. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk