From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs26339bki; Thu, 19 Aug 2010 05:43:40 -0700 (PDT) Received: by 10.224.78.194 with SMTP id m2mr6493266qak.19.1282221819419; Thu, 19 Aug 2010 05:43:39 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id i12si2792338qcb.188.2010.08.19.05.43.39; Thu, 19 Aug 2010 05:43:39 -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 E29CE19783D1; Thu, 19 Aug 2010 08:43:38 -0400 (EDT) X-Greylist: delayed 437 seconds by postgrey-1.31 at rubyforge.org; Thu, 19 Aug 2010 08:40:46 EDT Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 993E1185837B for ; Thu, 19 Aug 2010 08:40:45 -0400 (EDT) Received: by kuovi.tilus.net (Postfix, from userid 1000) id A3F1F1EF14; Thu, 19 Aug 2010 15:33:24 +0300 (EEST) From: Tero Tilus To: sup-talk In-reply-to: <1282214690-sup-777@eris> References: <1282214690-sup-777@eris> Date: Thu, 19 Aug 2010 15:33:24 +0300 Message-Id: <1282220267-sup-5326@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 Philipp, 2010-08-19 13:52: > Some clients seem to put the mailinglist in the CC field. Which is pretty annoying. > 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. > 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. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk