SNAC threw error: Not supported by host

[ufnddave]

I get this error when Adium starts up, connecting to one of my accounts. I think it's an AIM account. AIM now allows screen names with various punctuation marks, so I have a new screenname that is my email address, complete with "." and "@". I dismiss the error message and everything seems to be OK, but it pops up every startup. I can connect with the AIM client using the offending screenname just fine.

Sorry to bring it up here, but trac is busted...

[evands]

Out on a lark: Is your name entered into Adium with any capitalization or spacing?

[ufnddave]

Thanks Evands, but no, no caps or spaces. The account that gets the error is formatted with a screenname like "firstlast@domain.com". Other accounts work fine (one other AIM screenname) and I can connect without error through the AIM client.

I thought you had the answer there since I remember seeing similar problems with .Mac some time ago. Thanks for the suggestion.

[The_Tick]

It'll sound weird, but see if you can enter the account information into the .mac account type we have. I don't remember if we even allow it in .89.1, but it may work.

[ufnddave]

It'll sound weird...

Yeah it did But I still get an error... I WAS partially successful in that I was able to create a new Adium account as a .mac type with the same information as the offending AIM screenname ("firstlastname@domain.com"). Of course I received a GAIM error that authentication failed because I don't have a .mac account, but Adium took me all the way there.

I also experimented with enabling/disabling different accounts in different combinations (AIM and .mac on; AIM on, .mac off; etc.) -- that doesn't seem to change anything.

What does seem weird to me is that .mac uses the same login server as AIM. Is that right? Hmm...maybe that's why you suggested the same info. for the .mac account type...

Thanks for the suggestion, Tick. I hope the information above is helpful in some way.

[evands]

The .Mac account type is adding an @mac.com to your name internally in an attempt to be helpful, since you didn't do it yourself ;-) That, of course, means that an invalid name is sent to the server.

Does the Adium 1.0 Beta work properly for you with this name? Trac is down, so direct link to a slightly modified version of the current beta release:
http://evands.penguinmilitia.net/Adium_1.0b14-2.dmg

[The_Tick]

Eh, was worth a shot right

[evands]

Eh, was worth a shot right

I think that if it didn't add the @mac.com, it would connect and not through the SNAC not supported... but then again, it shouldn't be complaining (if that's right) with it entered with no capitalization, either, so maybe not.

[ufnddave]

Good News! The 1.0 beta works fine with the aim name that .89.1 didn't like.

I had to diddle with the preferences a bit to put Adium back together the way I like it, but it seems to be working fine.

Thanks! Any reason to go back to the official release version?

[ontology]

I get this error when Adium starts up, connecting to one of my accounts. I think it's an AIM account. AIM now allows screen names with various punctuation marks, so I have a new screenname that is my email address, complete with "." and "@".

Yes this is happening to me too. At first I thought it was because I had the same email address for both my gmail and my AIM accounts, so then I made a whole new email-based AIM account, and the error still occured.

Are we sure that if I'm getting this error, at least I'm still logged in and can communicate normally on the AIM network?

[evands]

1) Please try the AdiumBeta at http://beta.adiumx.com and let us know if it fixes the problem
2) Yes, you're logged in normally despite the error message.

[nessahead]

I did the update to 1.0 and am now getting this error every 5 minutes or so. My AIM username is vmillsj2. Any ideas on a fix?