RFC 3920: 11.2, says xml-names is to be used, xml-names, section: 4.1, Namespace Constraint: Prefix Declared, says:    The namespace prefix, unless it is <code>xml</code> or <code>xmlns</code>, must have been declared in a <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/#dt-NSDecl">namespace declaration</a> attribute in either the start-tag of the element where the prefix is used or in an an ancestor element (i.e. an element in whose <a href="http://www.w3.org/TR/REC-xml#dt-content">content</a> the prefixed markup occurs). That pretty much sums it up, actually, xml-names goes on to say:    This constraint may lead to operational difficulties in the case where the namespace declaration attribute is provided, not directly in the XML <a href="http://www.w3.org/TR/REC-xml#dt-docent">document entity</a>, but via a default attribute declared in an external entity. Such declarations may not be read by software which is based on a non-validating XML processor. Many XML applications, presumably including namespace-sensitive ones, fail to require validating processors. For correct operation with such applications, namespace declarations must be provided either directly or via default attributes declared in the <a href="http://www.w3.org/TR/REC-xml#dt-doctype">internal subset of the DTD</a>. So please go and log a bug against ejabberd. <div class="gmail_quote">On Fri, Feb 29, 2008 at 3:45 PM, Sergei Golovan <<a href="mailto:sgolovan@nes.ru">sgolovan@nes.ru</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On 2/29/08, Norman Rasmussen <<a href="mailto:norman@rasmussen.co.za">norman@rasmussen.co.za</a>> wrote: > The point is that: > > <stream:stream > xmlns:stream='<a href="http://etherx.jabber.org/streams%27" target="_blank">http://etherx.jabber.org/streams'</a>> > <message><gajim:die/></message> > </stream> > > contains an unbound prefix 'gajim', so MUST be rejected by all XMPP > parsers..  If you want to send xml that looks similar to that, you need to > transmit one of the following: </div>Just find any rule in RFC 3290 which forbids this stanza with unbound prefix and I'll immediately file a bugreport to ejabberd. -- Sergei Golovan </blockquote></div> -- - Norman Rasmussen - Email: <a href="mailto:norman@rasmussen.co.za">norman@rasmussen.co.za</a> - Home page: <a href="http://norman.rasmussen.co.za/">http://norman.rasmussen.co.za/</a>