Fire not showing up as away on AIM

Michael Park <[email protected]>
Newsgroups gmane.network.fire.general
Message-ID <a05210600bc08b1f9f8d7@[69.75.33.226]>
Been having a little trouble with Fire's away status.  When I set 
myself as away using Fire, all my AIM buddies still see me as being 
available.  I tested this myself by logging one account in using Fire 
and another account using the official AIM client.  I set the account 
that was using Fire to Away status with a particular message, but 
when I tried getting info on the Fire account using the official AIM 
client, it made absolutely no indications that I was actually away. 
I couldn't even see the away message I set for myself.

I also tested this using naim... it doesn't see my Fire account's 
away message/status either.  The only way my AIM buddies know I'm 
Away when I set myself to Away is when they get an autoresponse after 
trying to message me when I set myself as Away.

Additionally, the official AIM client does not see my Fire account's 
profile at all.  Neither does it receive the Buddy Icon I set for 
that account either...

Is it some sort of misconfiguration error on my part or have others 
been having these problems?

I'm using a CVS build that dates back several days... had the same 
issues with the 1.0 alpha too.

Any help would be greatly appreciated.  Thanks a lot!


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Fire-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fire-talk
Have a question? Please read the Fire Frequently Asked Questions:
http://fire.sourceforge.net/faq.shtml
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.