From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs602351agc; Fri, 23 Oct 2009 14:23:59 -0700 (PDT) Received: by 10.224.79.22 with SMTP id n22mr5737083qak.230.1256333037465; Fri, 23 Oct 2009 14:23:57 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si3042983qwk.24.2009.10.23.14.23.56; Fri, 23 Oct 2009 14:23:57 -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 A2DE43C8047; Fri, 23 Oct 2009 17:23:56 -0400 (EDT) X-Greylist: delayed 540 seconds by postgrey-1.31 at rubycentral.org; Fri, 23 Oct 2009 17:22:38 EDT Received: from everglades.pioto.org (everglades.pioto.org [207.192.69.249]) by rubyforge.org (Postfix) with ESMTP id 683F01858289 for ; Fri, 23 Oct 2009 17:22:39 -0400 (EDT) Received: by everglades.pioto.org (Postfix, from userid 81) id B288F1604EC; Fri, 23 Oct 2009 17:13:35 -0400 (EDT) To: MIME-Version: 1.0 Date: Fri, 23 Oct 2009 17:13:35 -0400 From: Mike Kelly Message-ID: <2aeb4e149305569502f106c7e54ae107@localhost> X-Sender: pioto@pioto.org User-Agent: RoundCube Webmail/0.3-stable Subject: [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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi, I seem to be caught in a bit of a catch-22. I can't reliably use mbox because of shortcomings in its format. And, I can't use maildir because sup-sync-back doesn't support it. More specifically, I seem to come across this much more often that I should. It's caused by someone starting a line of their message with "From". For example: ... X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.0 Status: X-Keywords: Content-Length: 1742 From the ticket he states that 1.2.3.4 is the IP: ... That yields this exception: [Fri Oct 23 17:07:00 -0400 2009] unlocking /usr/home/staff/mike/.sup/lock... /usr/local/lib/ruby/1.8/time.rb:184:in `local': argument out of range (ArgumentError) from /usr/local/lib/ruby/1.8/time.rb:184:in `make_time' from /usr/local/lib/ruby/1.8/time.rb:243:in `parse' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mbox.rb:15:in `is_break_line?' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mbox/loader.rb:165:in `next' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mbox/loader.rb:145:in `synchronize' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mbox/loader.rb:145:in `next' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/source.rb:103:in `each' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:560:in `send' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:560:in `__pass' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:547:in `method_missing' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:139:in `each_message_from' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:520:in `send' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:520:in `method_missing' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:146 from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:141:in `each' from /usr/home/staff/mike/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:141 from /usr/home/staff/mike/lib/ruby/gems/1.8/bin/sup-sync:19:in `load' from /usr/home/staff/mike/lib/ruby/gems/1.8/bin/sup-sync:19 Is there much of anything that I can do to mitigate this problem, aside from manually altering every offending message? It seems like the messages' Content-Length header should be used to skip past the body and ignore the offending Froms? Or, at least, if that sort of ArgumentError is thrown, maybe it should be caught and handled better? I'm running current master (2dfd378b616243d03203e49f5ee29636051d3cbf). Thanks. -- Mike Kelly _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk