[jdev] RFC 3921 message to RFC 5322 message conversion

chris johnston ctofur at gmail.com
Tue Jan 5 06:44:25 CST 2010


You may want to investigate the transport
http://xmpppy.sourceforge.net/mail/  for a base application to improve as
you need.
 I have used this transport with eJabberD and is very simple to setup.


-Chris


On Tue, Jan 5, 2010 at 5:02 AM, Tomasz Sterna <tomek at xiaoka.com> wrote:

> Hello.
>
> I am working on accessing jabber message archive with IMAP and a normal
> MUA with IMAP backend.
>
> This begs a question: How do I convert RFC 3921 message, to RFC 5322
> message to store in IMAP store. (But it may also be useful for
> Jabber/E-Mail gateway.)
>
> 1. How do i store 'from' and 'to' fields of the XMPP message?
> RFC 5322 defines From: as mailbox-list and To: as address-list which in
> turn reduces to addr-spec which does not include schema and is assumed
> to be in SMTP domain. ":" is used to delimiter group names so we cannot
> use XMPP URI there.
> - Should I add X- header for preserving XMPP 'from' field? What exact?
> - Should I fill From: and To: fields to maka maile readers usable?
>
> 2. Subject: header is straightforward
>
> 3. <thread/> converts directly to References:
> - what if there is no <thread/>? Should I supplement it? How?
>
> 4. Should I generate Message-ID header? If so, how? Maybe it would be
> useful to base it on some of the message characteristics?
>
>
>
>
> --
> Tomasz Sterna
> Xiaoka.com
>
> _______________________________________________
> JDev mailing list
> Forum: http://www.jabberforum.org/forumdisplay.php?f=20
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20100105/d98e2d24/attachment.htm>


More information about the JDev mailing list