Bad protocol from MANAGESIEVE server: EOL2

[David Arndt]

   Hi,

   Quoting Alain Spineux <aspineux at gmail.com>:

> Hi
>
> Did you look if sieve is up and running ?
> # netstat -a  -p | grep sieve
> tcp        0      0 *:sieve                     *:*
> Â  Â  Â  LISTENÂ  Â  Â  28460/cyrmaster
> tcp        0      0 *:sieve                     *:*
> Â  Â  Â  LISTENÂ  Â  Â  28460/cyrmaster

   I didn't get any output. This mean sieve is not listing to any  
port? But why, I didn't change anything on the configuration of the  
Kolab-Server.

   An additonal info: The active sieve scripts on the server works.
>
> Did you googled about your error message.
> I found this : http://www.cwinters.com/news/display/893
> Can you check ?

   Yes, I googled and read this, but it's no solution for me.

   Regards, David.
>
>
> On 10/14/07, David Arndt <arndt at map2net.de> wrote:
>>
>>
>> Hi,
>>
>> since a few days I get the error: "Bad protocol from MANAGESIEVE server:
>> EOL2" when I try to connect to sieveshell. I don't know to manage the
>> problem, in the logs of cyrus, I cannot find any errormessage.
>>
>> I run the Kolab 2.1.0
>>
>> Regards, David.
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>>
>>
>
>
> --
> Alain Spineux
> aspineux gmail com
> May the sources be with you
>


-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: http://kolab.org/pipermail/kolab-users/attachments/20071015/952721e6/attachment-0001.html
-------------- nächster Teil --------------
Ein Dateianhang mit Bin�rdaten wurde abgetrennt...
Dateiname   : nicht verf�gbar
Dateityp    : application/pgp-keys
Dateigr��e  : 1320 bytes
Beschreibung: =?utf-8?b?w5ZmZmVudGxpY2hlciA=?=
	=?utf-8?b?UEdQLVNjaGzDvHNzZWw=?=
URL         : http://kolab.org/pipermail/kolab-users/attachments/20071015/952721e6/attachment-0001.bin