From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs417384agc; Sun, 1 Nov 2009 11:03:02 -0800 (PST) Received: by 10.224.0.157 with SMTP id 29mr2341222qab.373.1257102182115; Sun, 01 Nov 2009 11:03:02 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 12si6528184qyk.81.2009.11.01.11.03.01; Sun, 01 Nov 2009 11:03:02 -0800 (PST) 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 5BE7715B8027; Sun, 1 Nov 2009 14:03:01 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3EFB6185826F for ; Sun, 1 Nov 2009 13:46:34 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N4fRh-0007K8-Hn for sup-talk@rubyforge.org; Sun, 01 Nov 2009 10:46:33 -0800 From: William Morgan To: sup-talk In-reply-to: <2aeb4e149305569502f106c7e54ae107@localhost> References: <2aeb4e149305569502f106c7e54ae107@localhost> Date: Sun, 01 Nov 2009 10:46:33 -0800 Message-Id: <1257101109-sup-4117@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] mbox date fail 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 Reformatted excerpts from Mike Kelly's message of 2009-10-23: > Is there much of anything that I can do to mitigate this problem, > aside from manually altering every offending message? I've fixed this in master. Can you try again, please? > It seems like the messages' Content-Length header should be used to > skip past the body and ignore the offending Froms? This is an option, but I'm avoiding it, because Content-Length is not guaranteed to be there, and not guaranteed to be correct. > Or, at least, if that sort of > ArgumentError is thrown, maybe it should be caught and handled better? Yep, that's what I've done. I couldn't get my local system to throw ArgumentError, even with your example, but if it's possible, it's possible, and should be caught. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk