using fully qualified email address as XMPP username

[Paul Aurich]

On Sep 23, 2009, at 14:57, Brady J. Frey wrote:
> Good afternoon everyone,
> We've been slowly migrating our users worldwide off of the Windows  
> platform, but had a bit of a problem using our own custom Jabber  
> server with Pigin. We have multiple domains, so we use fully  
> qualified email addresses as the username, thus:
>
> bob.joe at mydomain.com
>
> ...would be the full username. Of course, everytime we do that,  
> Pigin pulls the domain out and pops it into the domain field,  
> regardless if that field is already full.
>
> Anyone know of a workaround so that I can get an ampersand as part  
> of the username? Thank you!
>
> Brady J. Frey


The short answer is you probably need to enter the usernames as  
"bob.joe\40mydomain.com" (replace '@' with "\40").  An '@' is not a  
legal character in the Jabber ID node (username).

Just to make sure, though, are each of these domains configured as a  
vhost on the XMPP server? IOW, does the XMPP server think it is the  
authoritative server for mydomain.com (et al)? If so, you want to set  
up the accounts as:
	Username: bob.joe
	Domain: mydomain.com
and on the Advanced Tab:
	Connect Server: our-jabber-server.blah.internal  (this causes Pidgin  
to connect directly to this server instead of relying on the results  
of a SRV lookup on _xmpp-server._tcp.mydomain.com).

~Paul