<?xml version="1.0" encoding="UTF-8"?>
<rss version="0.92"
        xmlns:content="http://purl.org/rss/1.0/modules/content/"
        xmlns:wfw="http://wellformedweb.org/CommentAPI/"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<channel>
        <title>deep darc » eMail via XMPP » Comments</title>
        <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/</link>
        <description>deep and darc stuff</description>
        <lastBuildDate>Tue, 28 Oct 2008 15:55:23 +0000</lastBuildDate>
        <docs>http://backend.userland.com/rss092</docs>
        <language>en</language>

                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>cheney</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-836</link>
            <description><![CDATA[<p>To be more successful you would need something like mail markup language.  I am currently considering writing a mail specific protocol.  It would be XMPP based but appears to operate like SMTP.</p>

<p>http://mailmarkup.org/</p>
]]></description>
            <pubDate>Tue, 28 Oct 2008 15:55:23 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>brett</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-805</link>
            <description><![CDATA[<p>Very interesting stuff.  I guess the reverse would be fairly easy.  Any suggestions on how to deal with forwards, bcc's, and emails as attachments?</p>
]]></description>
            <pubDate>Tue, 01 Jul 2008 14:19:11 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>sander</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-458</link>
            <description><![CDATA[<p>fyi: <a href="http://users.telenet.be/s.devrieze/imail/imail.pdf">http://users.telenet.be/s.devrieze/imail/imail.pdf</a></p>

<p><a href="http://www.3pblog.net/index.php?entry=entry050702-180443">http://www.3pblog.net/index.php?entry=entry050702-180443</a></p>
]]></description>
            <pubDate>Fri, 02 Jun 2006 21:08:08 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>haiku</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-383</link>
            <description><![CDATA[<p>Repalcing MIME with XML is not a good idea... legacy mail – to – XMPP gateways will have to spend a lot of resources repacking messages. It's better to just transfer the messages without too much processing</p>
]]></description>
            <pubDate>Mon, 10 Apr 2006 17:05:24 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>mibus</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-320</link>
            <description><![CDATA[<p>I'd spell things out in full - &lt;header&gt; and &lt;body&gt; not &lt;h&gt; and &lt;b&gt;. It seems the Jabbery way <img src="http://www.deepdarc.com//images/smilies/6.png" alt=";)" style="border: 0; margin-bottom: -4px;" /></p>

<p>I've actually played with a similar idea (replacing SMTP with XMPP entirely)
http://mibus.cgcommunity.com/index.php?id=405</p>

<p>I went a different route though, using &lt;message&gt;'s. XMPP already supports alot of the stuff you're trying to wrap up (from, to - albeit not with names etc.).</p>
]]></description>
            <pubDate>Wed, 05 Apr 2006 22:43:45 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>darco</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-319</link>
            <description><![CDATA[<p>There is certainly much, much more work to be done. This isn't even a protocol–this is just the first step. This post is just to get the ball rolling. <img src="http://www.deepdarc.com//images/smilies/1.png" alt=":)" style="border: 0; margin-bottom: -4px;" /></p>

<p>I have already written an XSL transform for converting XML-MIME to MIME.  I'll be posting more information on all of this when I can get some time.</p>

<p>Gosh it would be nice to get paid for this stuff. (Google? You listening? I'd be happy to move back to Seattle. <img src="http://www.deepdarc.com//images/smilies/7.png" alt=":D" style="border: 0; margin-bottom: -4px;" />)</p>
]]></description>
            <pubDate>Wed, 05 Apr 2006 20:51:05 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>Jean-Louis Seguineau</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-316</link>
            <description><![CDATA[<p>In addition to what Nolan said, I suggest you have a look at <a href="http://www.jabber.org/jeps/jep-0131.html">JEP-0131: Stanza Headers and Internet Metadata (SHIM)</a> for a way to represent 'standard' headers...</p>

<p>As to the support by clients, this would either have to be built into new clients (new protocol implies new client support), or left to some server component to translate.</p>

<p>My 2cts. Keep going</p>
]]></description>
            <pubDate>Wed, 05 Apr 2006 11:53:29 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>Nolan Eakins</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-315</link>
            <description><![CDATA[<p>You have more work than that. The major problem with a direct translation of the MIME email to an XML-MIME email is that clients don't and won't support it, though XSLT could help convert.</p>

<p>You'll need to get very friendly with a number of JEPs to get this going. For starters: extended stanza addressing (-0033), XHTML-IM (-0071), publishing stream requests (-0137), and file transfer (-0096).</p>

<p>Best of luck! This could be a boon.</p>
]]></description>
            <pubDate>Wed, 05 Apr 2006 09:26:22 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>darco</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-314</link>
            <description><![CDATA[<p>I agree, and I'm working that into the spec now.</p>
]]></description>
            <pubDate>Sun, 02 Apr 2006 00:48:58 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>adruab</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-313</link>
            <description><![CDATA[<p>It seems like content related tags would be better as attributes.  That's assumes they're not oft extended and can't have multiple instances in mime specification.</p>
]]></description>
            <pubDate>Sat, 01 Apr 2006 23:10:07 +0000</pubDate>
        </item>
                
        <item>
            <title>RE: eMail via XMPP</title>
            <dc:creator>fireflysoup</dc:creator>
            <link>http://www.deepdarc.com/2006/03/30/email-via-xmpp/#comment-312</link>
            <description><![CDATA[<p>Smarty Pants!</p>

<p>:P</p>
]]></description>
            <pubDate>Thu, 30 Mar 2006 22:26:16 +0000</pubDate>
        </item>
        
</channel>
</rss>
