Cannot add Jabber Buddy

Question

Cannot add Jabber Buddy

I'm connected to a Jabber server through my office. I can see three Jabber users on the same server. Another can see me and can initiate a chat with me, but I cannot add him as a buddy. He was a buddy at one time, but dropped off my list. He's in my address book and when I click on the plus to add or Add buddies under the Buddies menu, I can see his screen name, but he doesn't show up in my Jabber List.

Any ideas?

Thanks,
Patty

MacBook Pro Mac OS X (10.4.7)

MacBook Pro, Mac OS X (10.4.7)

Posted on Jul 19, 2006 3:45 PM

Reply

Answer 1

Jul 20, 2006 12:23 PM in response to Patty Hudson1

Hi Patty,

Welcome to the Apple Discussions

This sounds like a Buddy is either Blocking you or you, them.

Go to the iChat View menu.
Select Show Off Line Buddies
Does the Buddy now appear in pale grey text ?

If this is the case go to iChat > Preferences > Accounts
Select the Jabber account in the list on the left
Select Security tab on the right
Make sure Allow All or Allow Buddy list is selected.

In the Address Book check the spelling of the Jabber name.

In iChat if you can see the Buddy's name check it is spelt correctly.
Also highlight the Buddy and use the Apple and i keys together (Get Info)
Select the Account name in the drop down.
Check the screen Jabber name here as well.

8:23 PM Thursday; July 20, 2006

Reply

Answer 2

Jul 20, 2006 1:08 PM in response to Ralph-Johns-UK

Done on my side.

I just checked with the "problem" Jabber buddy (by email). He's able to see me and initiated a chat to tell me he isn't blocking me. I did find out that he is using Exodus as a client, while the three that I can see are using Gaim. Is there any specific non-compatibility issues with different Windows clients?

Thanks,
Patty

Reply

Answer 3

Jul 20, 2006 3:47 PM in response to Patty Hudson1

HI Patty,

Not that I know of.

11:47 PM Thursday; July 20, 2006

Reply

Answer 4

Sep 6, 2006 7:02 AM in response to Patty Hudson1

My setup: iChat server on 10.4 Server (all patched up), iChat 3 on an intel iMac, running the latest everything.

I am also having this problem. Though, I have a slightly more specific set of symptoms. When the one affected buddy is offline, and I sign on, I see them as not being signed on. As soon as he signs on, his name gets dropped from my list. I've tried dumping all the iChat cache/icon/pref files I can find, to no avail. What's more, I can log in using trillian from my PC, and all contacts show up perfectly. This looks to be very much an iChat client problem, but I still have a slight suspicion that it might be some crazy bit of stuff cached on my local iChat server.

For reference, iChat doesn't seem to put anything of interest out to the console when he logs on (which makes his name disappear on my end). The server logs show nothing unusual. Other users on the same server have no problem seeing him. Chats and video conferenced initiated by him or through other people (multi-person video conference) work fine, but I can't see him to initiate anything.

Reply

Answer 5

Sep 6, 2006 8:11 AM in response to Patty Hudson1

I finally got the answer to my issue from the admin of the Jabber server. It looks like from iChat, I can't really add buddies. They can invite me and I can accept. In my case the buddy had invited me using caps in his name, which worked until the server was changed to only lower case. The name in my buddy list had to be changed at the server level.

Reply

Answer 6

Sep 6, 2006 8:48 AM in response to Patty Hudson1

I thought it had something to do with capitol letters... but I managed to fix it up by deleting my user xml file on the server and logging back in again. It got recreated and all now works. Thinking back, I believe the one affected buddy was added with a capitol letter in his name.

The files are in /var/jabber/spool/<domain name>/

There should be a single xml file for each user. Looking at the contents of my file, it seems that the one affected user was placed outside the xml tag structure that lists buddies. I don't know if this is a total fluke or a real bug, but it's fixed now. 😉

Reply