[JDEV] why the new version of the AIM Transport is still being rejected by AOL?

[Jens Alfke]

Dixon Canario <dixtigger at yahoo.com> wrote:

> Anyone Knows why the new version of the AIM Transport is
> sending this message isn't this suppose to be fixed or is
> aol now doing to Jabber.org the same that they did to
> Odigo.com ???

The friendly folks at AOL late last week started blocking libfaim (used in
gaim and Fire as well as presumably the Jabber AIM transport).

Top of tree gaim sources (at sourceforge.net) generally have the latest
workarounds. You'll have to dig into the oscar subtree, most likely. Last I
heard there was a new block added yesterday but as of this morning gaim had
a workaround. This tit-for-tat cycle is likely to continue since AOL has
infinite resources to throw at it and no more reason to be interested in
openness (courtesy of the FCC).

"ALL YOUR BUDDY ARE BELONG TO US"  --AOL

--Jens