[Standards-JIG] Re: Syntax for forwarding messages
stpeter at jabber.org
Thu Jan 20 15:56:58 UTC 2005
In article <opskwdwi0qqj7son at smtp.chello.nl>,
"Tijl Houtbeckers" <thoutbeckers at splendo.com> wrote:
> On Thu, 20 Jan 2005 07:11:56 +0200, Stephen Marquard <scm at marquard.net>
> >> In article <82777bea05011014364165ed89 at mail.gmail.com>,
> >> Joe Hildebrand <hildjj at gmail.com> wrote:
> >>> It's just ask stpeter nicely to add type='oto' and type='ofrom' to
> >>> JEP-33.
> > Peter Saint-Andre wrote:
> > > So 'oto' is the original "to" address and 'ofrom' is the original
> > "from"
> > > address?
> > >
> > > /psa
> > >
> > Though please can we have some mechanism to detect & prevent forwarding
> > loops, e.g. jid A is set to autoforward to jid B, which is set to
> > autoforward to jid A.
> > There needs to be a forwarding history in the message (with each
> > forwarding action adding a new entry) and/or a hop count. Servers should
> > stop forwarding and bounce the message (or take other action) when the
> > hop count exceeds a certain threshold and/or a forwarding loop is
> > detected.
> > The email equivalent is to check the number of Received: lines (in most
> > SMTP servers) or use unstandardised header extensions like X-Loop:.
> Well, there's an idea. Just use the same headers as email using SHIM. Then
> you don't have to modify JEP-33, which is more for for addresses that
> affect the routing at the XMPP level rather than the application level.
> Plus you'll get compatibility with email for free.
Sure, we'd use the Received SHIM header as mentioned in JEP-0131 and
defined in RFC 2822.
More information about the Standards