Comment 2 for bug 331940

The address was just a symptom :) The real cause was the login token which was added wrongly by the same code. The login token is used thusly:

the client randomly generates it and sends it to the server on login

the server, if > 0.2.8_somealpha, copies it over to the login accept message

if present in the login accept, the client compares it to the token it sent

Now, if the server doesn't reply with the token, but some code on the client adds it, the comparison fails and the client won't accept the login accept packet.

Anyway, the code adding default valued fields to received messages has been fixed, it would have caused no end of trouble in other areas as well.