2 djabberd patches

[Martin Atkins]

Hi Adrian,

I've checked in that second patch:
     <http://code.sixapart.com/trac/djabberd/changeset/771>

Thanks for looking at this. I'd noticed that Google's implementation was 
doing something weird, but I hadn't had time yet to figure out exactly 
what. This explains the weird behavior I've been seeing with dropped 
messages on my own server.

I'm not confortable checking in the second patch immediately because the 
comment before the line that sends <stream:features></stream:features> 
makes it look like this was originally added to fix some other problem. 
I wonder if anyone knows why we're currently sending this? Is there some 
other server implementation that falls over without it?

Cheers,
Martin

Adrian Ulrich wrote:
> Hi,
> 
> I've attached 2 djabberd patches, any chance to get them into svn?
> 
> 
> Patch: work_with_jabberd.diff
> --------------------------------
> DJabberd doesn't like to talk to jabberd servers out-of-the-box.
> Not sending '<stream:features></stream:features>' fixes this.
> 
> 
> Patch: gmail_vhosts.diff
> --------------------------------
> Google (and others?) are handling multiple domains/vhosts over one connection.
> (You'll get stanzas from @gmail.com and @$hosted_domain)
> DJabberd doesn't like this because verified_remote_domain will get overwritten multiple times.
> 
> My patch changes {verified_remote_domain} into a hashref to store multiple domains.
> (Is this 'the right thing to do' ? Well.. the patch seems to work for me)
> 
> 
> Regards,
>  Adrian
> 
> 
>