From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs176147vdc; Tue, 10 May 2011 11:00:09 -0700 (PDT) Received: by 10.224.182.211 with SMTP id cd19mr7480712qab.41.1305050409288; Tue, 10 May 2011 11:00:09 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t4si15914968qcs.63.2011.05.10.11.00.08; Tue, 10 May 2011 11:00:08 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id F359E18583B3; Tue, 10 May 2011 14:00:07 -0400 (EDT) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 0CD7B18583AB for ; Tue, 10 May 2011 13:38:29 -0400 (EDT) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1QJqzr-0007BJ-RS for sup-devel@rubyforge.org; Tue, 10 May 2011 17:45:23 +0000 From: William Morgan To: sup-devel In-reply-to: <1304373710-sup-1383@whisper> References: <1304373710-sup-1383@whisper> Date: Tue, 10 May 2011 17:45:23 +0000 Message-Id: <1305049400-sup-4316@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] [PATCH] Fix problem with time parsing X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion 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-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Reformatted excerpts from Hamish's message of 2011-05-02: > If a message has a date with month first and day second, then if the > day is greater than 12, heliotrope crashes. This patch catches the > error, and tries again after swapping the day and month. Is this a legitimate email message? Producing rfc2822-compliant date headers is one of the few things that everyone seems capable of doing besides spambots. I'm tempted to take the Sup approach of forging a date header, or giving up on the email, if it's unparseable. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel