From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.42.240.136 with SMTP id la8cs241771icb;
        Sun, 13 Feb 2011 10:49:20 -0800 (PST)
Received: by 10.224.6.72 with SMTP id 8mr2381938qay.175.1297622959700;
        Sun, 13 Feb 2011 10:49:19 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id r19si3256385qcs.100.2011.02.13.10.49.19;
        Sun, 13 Feb 2011 10:49:19 -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 4A3FF1858112;
	Sun, 13 Feb 2011 13:49:19 -0500 (EST)
Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.CMU.EDU [128.237.157.88])
	by rubyforge.org (Postfix) with ESMTP id 8604E1678325
	for <sup-talk@rubyforge.org>; Sun, 13 Feb 2011 12:39:10 -0500 (EST)
Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69)
	(envelope-from <rlane@zyrg.net>)
	id 1Pog0O-0000xa-Iv; Sun, 13 Feb 2011 12:45:04 -0500
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Tero Tilus <tero@tilus.net>
In-reply-to: <1297589599-sup-596@tilus.net>
References: <1297346751-sup-70@plc.intranet.plecavalier.com>
	<1297355619-sup-8657@bloovis.org>
	<1297356327-sup-9107@plc.intranet.plecavalier.com>
	<1297357197-sup-5893@bloovis.org>
	<1297364797-sup-8388@plc.intranet.plecavalier.com>
	<1297375381-sup-2823@plc.intranet.plecavalier.com>
	<1297560324-sup-4333@niflheimr> <1297589599-sup-596@tilus.net>
Date: Sun, 13 Feb 2011 12:45:04 -0500
Message-Id: <1297618949-sup-445@zyrg.net>
User-Agent: Sup/git
Cc: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] best method for before-add-message.rb
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=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 2011-02-13 04:51:02 -0500:
> Moritz Wilhelmy, 2011-02-13 03:34:
> > Can I pull arbitrary, parsed headers directly out of the message
> > object, or do I have to do my own parsing?
> 
> Uh, oh.  Looks like no, but it is pretty close, berause
> Message#parse_header already builds parsed hash of arbitrary headers
> internally.
> 

I use "hs = message.source.load_header(message.source_info)", which we
should probably make a convenience method on Message.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk