<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Receiving Email with Rails</title>
	<atom:link href="http://jasonseifer.com/2009/04/24/receving-email-with-rails/feed" rel="self" type="application/rss+xml" />
	<link>http://jasonseifer.com/2009/04/24/receving-email-with-rails</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 14:12:40 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: morgancurrie</title>
		<link>http://jasonseifer.com/2009/04/24/receving-email-with-rails/comment-page-1#comment-340</link>
		<dc:creator>morgancurrie</dc:creator>
		<pubDate>Fri, 24 Apr 2009 12:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://jasonseifer.com/?p=186#comment-340</guid>
		<description>how do you guys deal with stripping the quoted of the reply?</description>
		<content:encoded><![CDATA[<p>how do you guys deal with stripping the quoted of the reply?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: technoweenie</title>
		<link>http://jasonseifer.com/2009/04/24/receving-email-with-rails/comment-page-1#comment-339</link>
		<dc:creator>technoweenie</dc:creator>
		<pubDate>Fri, 24 Apr 2009 12:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://jasonseifer.com/?p=186#comment-339</guid>
		<description>Piping emails to a ruby process can present some scaling issues.  Each email is basically another ruby process that loads rubygems, tmail, mms2r, etc.  It&#039;s probably better to just have postfix dump emails to a maildir and have tmail read them in a little ruby daemon: &lt;a href=&quot;http://tmail.rubyforge.org/rdoc/classes/TMail/Maildir.html&quot; rel=&quot;nofollow&quot;&gt;http://tmail.rubyforge.org/rdoc/classes/TMail/M...&lt;/a&gt; .  I handled all of our email processing fine with ruby pipes for awhile.  But when I moved to our current host, they were quick to suggest using a maildir.&lt;br&gt;&lt;br&gt;I didn&#039;t know about mms2r, but I&#039;ll take a look at that.  I think I parse the mail parts manually with tmail right now, blah :)</description>
		<content:encoded><![CDATA[<p>Piping emails to a ruby process can present some scaling issues.  Each email is basically another ruby process that loads rubygems, tmail, mms2r, etc.  It&#39;s probably better to just have postfix dump emails to a maildir and have tmail read them in a little ruby daemon: <a href="http://tmail.rubyforge.org/rdoc/classes/TMail/Maildir.html" rel="nofollow"></a><a href="http://tmail.rubyforge.org/rdoc/classes/TMail/M.." rel="nofollow">http://tmail.rubyforge.org/rdoc/classes/TMail/M..</a>. .  I handled all of our email processing fine with ruby pipes for awhile.  But when I moved to our current host, they were quick to suggest using a maildir.</p>
<p>I didn&#39;t know about mms2r, but I&#39;ll take a look at that.  I think I parse the mail parts manually with tmail right now, blah <img src='http://jasonseifer.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: giles bowkett</title>
		<link>http://jasonseifer.com/2009/04/24/receving-email-with-rails/comment-page-1#comment-338</link>
		<dc:creator>giles bowkett</dc:creator>
		<pubDate>Fri, 24 Apr 2009 12:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://jasonseifer.com/?p=186#comment-338</guid>
		<description>hey jason - also check out Astrotrain on github. it receives e-mail and issues xmpp or http in response. blatant plug for my employer but it&#039;s what enables Tender to turn e-mails into support discussions. like how Tripit turns e-mails into itineraries automagically.</description>
		<content:encoded><![CDATA[<p>hey jason &#8211; also check out Astrotrain on github. it receives e-mail and issues xmpp or http in response. blatant plug for my employer but it&#39;s what enables Tender to turn e-mails into support discussions. like how Tripit turns e-mails into itineraries automagically.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
