<?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: eZ components &#8220;Mail&#8221; to save the day</title>
	<atom:link href="http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/feed/" rel="self" type="application/rss+xml" />
	<link>http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/</link>
	<description>Your freedom is worth more than you think. Take advantage of it while you can.</description>
	<lastBuildDate>Mon, 11 Jan 2010 00:29:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nerd Fish &#187; Blog Archive &#187; UTF-8 Email in PHP with eZ Components</title>
		<link>http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/comment-page-1/#comment-18</link>
		<dc:creator>Nerd Fish &#187; Blog Archive &#187; UTF-8 Email in PHP with eZ Components</dc:creator>
		<pubDate>Tue, 15 Aug 2006 04:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/#comment-18</guid>
		<description>[...] From browsing around the source (having been reminded by Jad Madi&#8217;s blog to take a look), the good news is it looks like eZ systems have this problem well solved. The ezcMail class, and related classes default to (assume) ASCII but you can explicitly tell it to use UTF-8 (note iconv is required) for subject, recipient, sender and body. In fact it&#8217;s a very impressive mail library all round, handling parsing as well as generating, multipart messages and all that. [...]</description>
		<content:encoded><![CDATA[<p>[...] From browsing around the source (having been reminded by Jad Madi&#8217;s blog to take a look), the good news is it looks like eZ systems have this problem well solved. The ezcMail class, and related classes default to (assume) ASCII but you can explicitly tell it to use UTF-8 (note iconv is required) for subject, recipient, sender and body. In fact it&#8217;s a very impressive mail library all round, handling parsing as well as generating, multipart messages and all that. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SitePoint Blogs &#187; UTF-8 Email in PHP with eZ Components</title>
		<link>http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/comment-page-1/#comment-16</link>
		<dc:creator>SitePoint Blogs &#187; UTF-8 Email in PHP with eZ Components</dc:creator>
		<pubDate>Mon, 14 Aug 2006 14:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/#comment-16</guid>
		<description>[...] From browsing around the source (having been reminded by Jad Madi&#8217;s blog to take a look), the good news is it looks like eZ systems have this problem well solved. The ezcMail class, and related classes default to (assume) ASCII but you can explicitly tell it to use UTF-8 (note iconv is required) for subject, recipient, sender and body. In fact it&#8217;s a very impressive mail library all round, handling parsing as well as generating, multipart messages and all that. [...]</description>
		<content:encoded><![CDATA[<p>[...] From browsing around the source (having been reminded by Jad Madi&#8217;s blog to take a look), the good news is it looks like eZ systems have this problem well solved. The ezcMail class, and related classes default to (assume) ASCII but you can explicitly tell it to use UTF-8 (note iconv is required) for subject, recipient, sender and body. In fact it&#8217;s a very impressive mail library all round, handling parsing as well as generating, multipart messages and all that. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PHPDeveloper.org</title>
		<link>http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/comment-page-1/#comment-15</link>
		<dc:creator>PHPDeveloper.org</dc:creator>
		<pubDate>Mon, 14 Aug 2006 12:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/#comment-15</guid>
		<description>&lt;strong&gt;Jad Madi&#039;s Blog: eZ components &quot;Mail&quot; to save the day...&lt;/strong&gt;

...</description>
		<content:encoded><![CDATA[<p><strong>Jad Madi&#8217;s Blog: eZ components &#8220;Mail&#8221; to save the day&#8230;</strong></p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derick</title>
		<link>http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/comment-page-1/#comment-13</link>
		<dc:creator>Derick</dc:creator>
		<pubDate>Mon, 14 Aug 2006 09:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://syntux.net/blog/2006/08/14/ez-components-mail-to-save-the-day/#comment-13</guid>
		<description>You can actually fetch a single email, but it seems that it is currently only implemented for the mbox transport. However, we are currently working on adding this method to the pop transport as well, and to add a new function to get a set of mail messages (similar to limit/offset).</description>
		<content:encoded><![CDATA[<p>You can actually fetch a single email, but it seems that it is currently only implemented for the mbox transport. However, we are currently working on adding this method to the pop transport as well, and to add a new function to get a set of mail messages (similar to limit/offset).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
