server error received ==== ....

[GoogleCodeExporter]

What steps will reproduce the problem?
1. type fast and alot in a conversation

What is the expected output? What do you see instead?
i expect to type and nothing will happend instead i get a messagebox on random 
moments that says server error receiver ===== ratelimit exceeded.

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
latest msnpsharp(may 16) win 7 visual studio.

Is your code check out from SVN or download from our download site?
download site

Please provide any additional information below:
theres a few more of these server error received ==== messageboxes like 
(something like) contactdoesntacceptIM's and invalidContactList... these 
messageboxes seem useless as my msn keeps on working. i cant find where i can 
put these off.

Original issue reported on code.google.com by sander-d...@hotmail.com on 31 May 2011 at 11:05

[GoogleCodeExporter]

im using MSNP-Sharp v4.0.1 for MSNP21 just to be clear, never had the problem 
with the other version. msnp18

Original comment by sander-d...@hotmail.com on 1 Jun 2011 at 10:05

[GoogleCodeExporter]

Original comment by freezing...@gmail.com on 1 Jun 2011 at 10:22

• Changed state: Accepted

[GoogleCodeExporter]

I think that's the problem in example client, it will send typing messages once 
the content of input box has been changed, so it will flood the msn server then 
you get the error message. Give me some time and have a check.

Original comment by freezing...@gmail.com on 1 Jun 2011 at 10:24

[GoogleCodeExporter]

ah ok, so i can put an interval into sending the typing notice. but sometimes 
it comes even when theres no typing going on wouldnt know how to reproduse that.

thanks for the reply!

Original comment by sander-d...@hotmail.com on 1 Jun 2011 at 10:30

[GoogleCodeExporter]

Hi,

For those error coming out without typing, that's because something goes wrong 
in the remote contact side (sometimes their p2p capacities doesn't match the 
protocol they supported), you can comment out line 1228 in DotMSNClient.cs or 
filter the useless error message there. BTW, I just make a commit for the 
typing message issue, you can use SVN to check it out in 
branches/MSNPSHARP_40_STABLE folder

Original comment by freezing...@gmail.com on 1 Jun 2011 at 10:39

[GoogleCodeExporter]

Or if it still doesn't fix the issue, would you please attach a trace log here?

Original comment by freezing...@gmail.com on 1 Jun 2011 at 10:40

[GoogleCodeExporter]

thanks again for the reply.

I'm not using the msnpsharp client directly though i have used it as an example 
to use your framework. i will try to check out the svn and that line in the 
dotmsnclient when im done with work.
if i still cant fix it i will attach a trace log.

thanks for the effort.

Original comment by sander-d...@hotmail.com on 2 Jun 2011 at 8:27

[GoogleCodeExporter]

Hi,
simply blocking out the line you said from the exceptionoccured event fixed the 
msgbox, thanks alot for pointing that out.

Original comment by sander-d...@hotmail.com on 5 Jun 2011 at 2:43

[GoogleCodeExporter]

Original comment by freezing...@gmail.com on 10 Jun 2011 at 2:15

• Changed state: WontFix