Logged In: YES 
user_id=12800

Oh sorry.  A domain literal is something like [192.168.1.2]
IOW, the IP address octets surrounded by square brackets. 
Should be easy enough to calculate.  Attached is a proposed
patch.

As for the privacy violation, I don't think it's on the same
level as the ftp issue because we're not divulging any
information about the user.  It could be argued that leaking
the hostname might be enough to link the information to a
specific user, and I might buy that argument, although it
personally doesn't bother me too much (the IP address might
be just as sufficient for linking and  even NAT'd or DHCP'd
addresses might be static enough to guess -- witness your
own supposedly dynamic IP address :).  And the IP will
always be available via the socket peer.

OTOH, Eduardo's claim isn't totally without merit.  I'd like
to be able to retain the ability to be properly RFC
compliant, but could accept that the default be
localhost.localdomain.  If you (Guido) have a suggestion for
an appropriate API for both these requirements, that would
be great.