Same problem over here, what shows up in the log for haze:
clientLogin response statusCode was 440 (0): <response xmlns="https://api.login.aol.com"> <statusCode>440</statusCode> <statusText>Invalid DevId</statusText> </response>
Google-Fu indicates that the problem is existent among libpurple users in general, Adium users apparently can't log in, too. Seems like ICQ banned the DevId used by libpurple.
Same problem over here, what shows up in the log for haze:
clientLogin response statusCode was 440 (0): <response xmlns="https:/ /api.login. aol.com"> 440</statusCode > Invalid DevId</statusText>
<statusCode>
<statusText>
</response>
Google-Fu indicates that the problem is existent among libpurple users in general, Adium users apparently can't log in, too. Seems like ICQ banned the DevId used by libpurple.