From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs1331770agb; Thu, 31 Dec 2009 15:37:22 -0800 (PST) Received: by 10.224.97.203 with SMTP id m11mr6684089qan.178.1262302642439; Thu, 31 Dec 2009 15:37:22 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 39si22389977qyk.118.2009.12.31.15.37.22; Thu, 31 Dec 2009 15:37:22 -0800 (PST) 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 23E3D15B802C; Thu, 31 Dec 2009 18:37:22 -0500 (EST) Received: from magnesium.club.cc.cmu.edu (MAGNESIUM.CLUB.CC.cmu.edu [128.237.157.15]) by rubyforge.org (Postfix) with ESMTP id AEF951858249 for ; Thu, 31 Dec 2009 18:37:19 -0500 (EST) Received: (qmail 32702 invoked from network); 31 Dec 2009 23:37:19 -0000 Received: from pion.club.cc.cmu.edu (HELO localhost.localdomain) (128.237.157.88) by magnesium.club.cc.cmu.edu with SMTP; 31 Dec 2009 23:37:19 -0000 From: Rich Lane To: sup-devel@rubyforge.org Date: Thu, 31 Dec 2009 15:36:48 -0800 Message-Id: <1262302618-20503-1-git-send-email-rlane@club.cc.cmu.edu> X-Mailer: git-send-email 1.6.3.3 Subject: [sup-devel] Ruby 1.9 encoding fixes 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 This patchset fixes the string encoding issues on Ruby 1.9.1. The general strategy is to treat raw messsages as binary and ensure that everything is passed through Iconv or String#ascii before being displayed or stored. I tested an earlier version of this patchset (with more debug checks) on around 700 thousand mails including plenty of spam. It'd be nice if someone tested signed/encrypted mails to make sure I didn't break anything there. The only effect on Ruby 1.8 should be asciifying the raw header/message view, and maybe a little speedup due to reusing the RMail message header instead of parsing it ourselves. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel