From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs29998bki; Thu, 19 Aug 2010 06:53:34 -0700 (PDT) Received: by 10.224.19.66 with SMTP id z2mr6516901qaa.187.1282226013461; Thu, 19 Aug 2010 06:53:33 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l4si2967667qck.161.2010.08.19.06.53.33; Thu, 19 Aug 2010 06:53:33 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DE3D519783C8; Thu, 19 Aug 2010 09:53:32 -0400 (EDT) Received: from mail-gy0-f178.google.com (mail-gy0-f178.google.com [209.85.160.178]) by rubyforge.org (Postfix) with ESMTP id 42215185835A for ; Thu, 19 Aug 2010 09:40:03 -0400 (EDT) Received: by gyc15 with SMTP id 15so750644gyc.23 for ; Thu, 19 Aug 2010 06:40:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:subject :from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=WZghiDqaoKx3thLoVzE6SE8EGFP9YHPbhD2WPQprxMU=; b=a6CM597cRyCs+Pu93+wTFjrbPUASQQi6sfdmGEGD34q8Ww3o3M/TT6vN8CHGtCwu+s IrDrucoXYxS90qNBepnzXvKIwZBE1aPk7WHSJs1HZenabEM5xhYES6sxvjcSgb925OnU RlNlfNOONriq4RS7r0xuwzWpyJmh3cFCEDVZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=La9TthGh14UTFjPolvBv4O+M046IVYM+EvUm3y+2bZhCC+7bSQlu9gxdFiT1UrIyPv /Q44dkYECclkdHHHIfV/4XuL2skI6z4k2+MO4VUnQPtf+fOPR/TEhL1lSUmL33f4HtW/ bJSgZvbiC84DU7XlOss4S7QMIpway0gRJbgX4= Received: by 10.100.244.1 with SMTP id r1mr11246087anh.96.1282225202209; Thu, 19 Aug 2010 06:40:02 -0700 (PDT) Received: from elly (DU148.N47.QueensU.CA [130.15.47.148]) by mx.google.com with ESMTPS id 14sm2532504ant.1.2010.08.19.06.40.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Aug 2010 06:40:01 -0700 (PDT) From: Israel Herraiz To: sup-talk In-reply-to: <1282221210-sup-5773@tilus.net> References: <1282214690-sup-777@eris> <1282218941-sup-4503@duck> <1282221210-sup-5773@tilus.net> Date: Thu, 19 Aug 2010 09:39:43 -0400 Message-Id: <1282224936-sup-2131@duck> 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 Excerpts from Tero Tilus's message of Thu Aug 19 08:49:21 -0400 2010: > Whoa! > > Mailing lists _can_ do that, but they should not. Ironically you > happend to mention one of the reasons why they should not. :D > > Let's consider the max damage done by modifying vs. not modifying > reply-to: If the header is unmangled the user may in certain > sircumstances accidentally send private mail instead of list mail. > That's an annoyance at most. If the header is mangled by list server > the user may in certain sircumstances accidentally send list mail > instead of private mail. That may cost the user a lot of goodwill, > money or her job. Ergo, list setting reply-to header violates the > principle of least damage. Yes, that's one of the endless philosophical debates about email and mailing lists. I do actually agree with that, it is better not to set the Reply-To header. I was using as an example to show that Sup is behaving correctly in this case :-). Cheers, Israel _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk