Page 1 of 1

240 Error and disconnect when trying to Block

Posted: Tue May 19, 2009 2:53 pm
by Southpaw32
Whenever I try to block a user on the MSN service I receive a 240 Error and then MSN briefly disconnects. As well the contact isn't blocked.

I have tried deleting deleting the preferences files per http://trac.adium.im/wiki/Preferences, but that didn't work.

Any ideas?

Thanks!

Re: 240 Error and disconnect when trying to Block

Posted: Thu May 28, 2009 9:05 pm
by joecam010
I have had the same problem recently.

Running Adium 1.3.4 on OS X 10.5.7

I have been getting a lot of spam messages and while it is probably pointless doing so, I block the user and close the window (later I have a spring clean and clear the logs of these morons.)

Whenever I press the block button, all MSN contacts are logged off for as much as half a minute before Adium reconnects, and the Unknown Error (240) pops up.

Re: 240 Error and disconnect when trying to Block

Posted: Thu May 28, 2009 9:14 pm
by joecam010
Further to my previous post on this issue:

When I click the block button, Growl shows a window with the message "Unable to add User" before the unknown error (204) message. Unable to add user is not showing in Adium's own message window.

Re: 240 Error and disconnect when trying to Block

Posted: Thu May 28, 2009 9:57 pm
by Dimmuxx
240 is hopefully be fixed in 1.4b4, 204 isn't.

Re: 240 Error and disconnect when trying to Block

Posted: Sat May 30, 2009 9:10 am
by JanC
With 1.3.4 on 10.4.11 I get "cannot add user (240)" from both Adium and Growl. And the disconnection.
1.4 is Leopard only, so I downgraded to 1.3.2.

Re: 240 Error and disconnect when trying to Block

Posted: Sat May 30, 2009 9:51 pm
by angelikgiraldo
Same problem here
(Mac OS X 10.4.11)

Re: 240 Error and disconnect when trying to Block

Posted: Thu Jun 11, 2009 6:30 pm
by Southpaw32
I installed the new update, but still having this same issue.
Any ideas?

Thanks!

Re: 240 Error and disconnect when trying to Block

Posted: Thu Jun 11, 2009 8:09 pm
by Dimmuxx
It will be fixed in 1.4b7.