[Standards] [jdev] RFC 3921 message to RFC 5322 message conversion

Peter Saint-Andre stpeter at stpeter.im
Tue Jan 5 13:09:16 UTC 2010

On 1/5/10 5:30 AM, Dave Cridland wrote:
> On Tue Jan  5 10:02:42 2010, Tomasz Sterna wrote:


> I had some thoughts on this. The trickiest part is that the form of an
> XMPP address differs radically from that of an email address, although
> superficially both look identical.
>> 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?
> I'd opt for a simple tranformation of the address into an email
> compatible form. Alexey may have some good advice here, as he's been
> heavily involved in EAI. Pete Resnick, who edited RFC 5322, may also
> have some good ideas, and he's familiar with XMPP, having co-chaired the
> original XMPP WG.

See also the address conversion rules for XMPP to SIP:


Given that SIP addresses are (mostly) derived from email addresses, many
of the same rules should apply.


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6820 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20100105/9e416e62/attachment.bin>

More information about the Standards mailing list