problem signing into aim

[Josh Ribakoff]

Solved my problems too!

On Tue, Feb 9, 2010 at 3:31 PM, Scott Ebersold <scottebersold at me.com> wrote:

> Thank you!
>
> On Tuesday, February 09, 2010, at 03:08PM, "Evan Platt" <
> evan at espphotography.com> wrote:
> >Go to Accounts, Manage Accounts, select account, Advanced, uncheck Use
> >clientLogin.
> >
> >On 2/9/2010 12:06 PM, Scott Ebersold wrote:
> >> Hello.
> >>
> >> Until today, I've used pidgin to sign into AIM, gmail and MSN chats.
>  Today I cannot sign into AIM.  I've used the debug window but don't know
> what it means.
> >>
> >> Can someone please advise?  I've pasted the debug info below:
> >>
> >> (15:01:21) oscar: startOSCARSession response statusCode was 400:<?xml
> version="1.0" encoding="UTF-8"?>
> >> <response xmlns="http://developer.aim.com/xsd/aim.xsd"><statusCode>400</statusCode><statusText>useTLS=1
> is not allowed for non secure
> requests.</statusText><data><ts>1265745681</ts><upgradeData></upgradeData><betaData></betaData></data></response>
> >> (15:01:21) connection: Connection error on 0241D908 (reason: 16
> description: Received unexpected response from
> http://api.oscar.aol.com/aim/startOSCARSession)
> >> (15:01:21) jabber: jabber_actions: have pep: NO
> >> (15:01:21) account: Disconnecting account scootbugz (00CA1790)
> >> (15:01:21) connection: Disconnecting connection 0241D908
> >> (15:01:21) oscar: Signed off.
> >> (15:01:21) jabber: jabber_actions: have pep: NO
> >> (15:01:21) connection: Destroying connection 0241D908
> >> (15:01:26) util: Writing file accounts.xml to directory C:\Documents and
> Settings\sectemp\Application Data\.purple
> >> (15:01:26) util: Writing file C:\Documents and
> Settings\sectemp\Application Data\.purple\accounts.xml
> >
> >
> >
>
> _______________________________________________
> Support at pidgin.im mailing list
> Want to unsubscribe?  Use this link:
> http://pidgin.im/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/support/attachments/20100209/25e06c23/attachment.html>