On Sat, Mar 07, 2009 at 08:32:43PM -0500, Sean Sullivan wrote:
> To whom it may concern,
>
> Up until recently, Pidgin 2.5.5 was working out great for me until I started
> getting a WinSock error #10051 while attempting to sign into my AIM
> account. I am not sure if this is an issue on my end, o
To whom it may concern,
Up until recently, Pidgin 2.5.5 was working out great for me until I started
getting a WinSock error #10051 while attempting to sign into my AIM
account. I am not sure if this is an issue on my end, or the AIM servers,
but I would like some help trying to figure out what i
