From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs44050bki; Thu, 19 Aug 2010 11:16:01 -0700 (PDT) Received: by 10.224.62.196 with SMTP id y4mr151165qah.171.1282241760283; Thu, 19 Aug 2010 11:16:00 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id d27si3590290qcs.46.2010.08.19.11.15.59; Thu, 19 Aug 2010 11:16:00 -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 B565319783D9; Thu, 19 Aug 2010 14:15:59 -0400 (EDT) Received: from tihlde.org (colargol.tihlde.org [158.38.48.10]) by rubyforge.org (Postfix) with ESMTP id A28D81858374 for ; Thu, 19 Aug 2010 14:09:32 -0400 (EDT) Received: by tihlde.org (Postfix, from userid 1623) id E7A0B1011E00; Thu, 19 Aug 2010 15:21:03 +0200 (CEST) From: Helge Titlestad To: sup-talk In-reply-to: <1282222218-sup-5975@tilus.net> References: <1282214690-sup-777@eris> <1282218941-sup-4503@duck> <1282220819-sup-9512@theshire> <1282221544-sup-9759@eris> <1282222218-sup-5975@tilus.net> Date: Thu, 19 Aug 2010 15:21:03 +0200 Message-Id: <1282223762-sup-1786@colargol.tihlde.org> User-Agent: Sup/0.11 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 Excerpts from Tero Tilus's message of Thu Aug 19 15:07:37 +0200 2010: > 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. > > 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. If sup is doing the removal of duplicates, could we get sup to update the List-* headers if there are any new ones? -- 77660 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk