[Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

[Wouter Berkepeis]

Hello Stephan,

Thanks for the answer. I also thought it should work this way. Thank you
for the suggestion using rawlog, hopefully I can find out why it does
not work (yet). Complicating factor is that I run 2 versions of
SmartSieve on two different machines, the old one for everyday use, and
the new one for testing inside my lan. Always a bit tricky these do not
interfere. For testing managesieve(-login) I also used the Thunderbird
sieve plugin. This is working ok for the new setup, I can actually log
in and send and save sieve settings on the server (a lot of s's...:-) ).
So Dovecot is working ok, it's the client side causing the problem.

Regards,

Wouter

On 10/07/2013 08:54 AM, Stephan Bosch wrote:
> On 10/7/2013 1:01 AM, Wouter Berkepeis wrote:
>> Everything OK I guess. Especially the first part of the output is
>> interesting: "IMPLEMENTATION" "Dovecot Pigeonhole"
>> This is what Smartsieve is looking at. With the former version the
>> string was 'dovecot', so I changed this in the 'Managesieve.php' file.
>> This file was already patched as stated on the site. Furthermore I
>> changed everything referring to port 2000 to port 4190.
> That should work. I used the patch mentioned here:
>
> http://www.mail-archive.com/dovecot@dovecot.org/msg21862.html
>
> And modified it for the new situation. I'm assuming this is very similar
> to what you're doing and here it works.
>
> You could try to obtain more information by logging the protocol exchange:
>
> http://wiki2.dovecot.org/Debugging/Rawlog
>
> Alternatively you can debug Smartsieve by adding more logging into the
> source code.
>
> And yes, SmartSieve is unmaintained, so I would not recommend using it
> anymore.
>
> Regards,
>
> Stephan.
>
>