Help - Search - Members - Calendar
Full Version: Annoying Horde error
The Planet Forums > Control Panels > Plesk
sisterscape
I don't know if this is the best place to post this. Please move if appropriate.

A few days ago I started getting this error on the 'Horde :: My Summary' page. I am now unable to see whether I have new messages from that page and so must go to my Inbox to check. Everything else seems to be working OK:

Notice: (null)(): [ALERT] Fatal error: TOO MANY CONSECUTIVE PROTOCOL VIOLATIONS: in Unknown on line 0

I'm hoping that someone here can tell me how to get it working
correctly again ie. displaying the number of new e-mails received.

Thanks!
4PSA
That's a IMAP problem, not horde. What version of Plesk do you use?
sisterscape
QUOTE
Originally posted by 4PSA
That's a IMAP problem, not horde. What version of Plesk do you use?
Thanks for responding. We are running 6.0.2. It was running fine then out of the blue . . .
4PSA
Try to restart courier-imap.
sisterscape
QUOTE
Originally posted by 4PSA
Try to restart courier-imap.
Courier-imap was restarted twice and it did not make any difference. icon_sad.gif
sisterscape
I finally solved the Horde problem! THE FILTERS ARE CAUSING IT!!!

A while back I recreated the account and all was fine for while. I had about ten filters and then when I added another one today I got the dreaded

"Notice: (null)(): [ALERT] Fatal error: TOO MANY CONSECUTIVE PROTOCOL VIOLATIONS: in Unknown on line 0"

message on the entry page again. I went back to the filter options, unchecked "Apply filter rules when mailbox is refreshed?" and am now no longer getting the error.

I have posted this to the Horde list so they will, hopefully, fix the filter/refresh code.
4PSA
It means that the filter sent invalid commands to the IMAP server. There are indeed about ten commands that can be sent before the protocol violation to occur.
sisterscape
QUOTE
Originally posted by 4PSA
It means that the filter sent invalid commands to the IMAP server. There are indeed about ten commands that can be sent before the protocol violation to occur.
The guys on the Horde list had this to say about my 'discovery':

1) Either your login parameters are bad or your c-client/PHP setup is buggy. Filtering is only displaying the problem - it is not the underlying cause of it.

2) You need to find out not what "triggers" the problem (filters being done) but what "causes" the problem (why does your imap server think bad commands are being sent?).

So they seem to think it's a problem with the way IMAP is set up not a problem with the filters themselves.

Anyone else care to jump in??
4PSA
A test should not be hard to do, it's enough to send the output of the filter code to the server (or better display it). You are logged in, this is not problem. Most likely it's a PHP warning displayed due to a PHP upgrade.
texasweb
A test should not be hard to do, it's enough to send the output of the filter code to the server (or better display it). You are logged in, this is not problem. Most likely it's a PHP warning displayed due to a PHP upgrade.

I just added a 10th filter and started getting the error from the original post. I remove 1 filter and don't get the error. How would I do what you suggested?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.