[Dovecot] managesieve proxy cyrus

[Mathieu Kretchner]

I've tried to take some data with tethereal :

The only data I'm able to see between cyrus and dovecot (without
protocol noise) :


Data (41 bytes)
0000  41 55 54 48 45 4e 54 49 43 41 54 45 20 22 50 4c   AUTHENTICATE "PL
0010  41 49 4e 22 20 22 41 47 6c 74 59 58 41 79 41 47   AIN" "AGltYXAyAG
0020  6c 74 59 58 41 79 22 0d 0a                        ltYXAy"..

Data (22 bytes)
0000  4f 4b 20 22 4c 6f 67 6f 75 74 20 43 6f 6d 70 6c   OK "Logout Compl
0010  65 74 65 22 0d 0a                                 ete"..


As you told me, the problem seems to be at authentication time. Whereas
I've found this in my imapd.conf of cyrus server :
# for sieveshell
sasl_mech_list: PLAIN


And in order to have a reference:  between dovecot proxy and imap dovecot :

Data (41 bytes)
0000  41 55 54 48 45 4e 54 49 43 41 54 45 20 22 50 4c   AUTHENTICATE "PL
0010  41 49 4e 22 20 22 41 47 6c 74 59 58 41 78 41 47   AIN" "AGltYXAxAG
0020  6c 74 59 58 41 78 22 0d 0a                        ltYXAx"..

Data (17 bytes)
0000  4f 4b 20 22 4c 6f 67 67 65 64 20 69 6e 2e 22 0d   OK "Logged in.".
0010  0a                                                .

Data (12 bytes)
0000  43 41 50 41 42 49 4c 49 54 59 0d 0a               CAPABILITY..







Mathieu Kretchner wrote:
> Stephan Bosch wrote:
>> Mathieu Kretchner wrote:
>>> Hello all,
>>>
>>> I've configured a dovecot server in proxy mode. It seems to work well
>>> but. I've tested managesieve with squirrelmail and it's working
>>> correctly but I can't connect to cyrus sieve server : timsieved
>> First of all, what versions are you using? How is it all configured? Do
>> the Dovecot and Cyrus logs contain anything useful?
> 
> I've to do a migration between cyrus and dovecot so we have choosen to
> use dovecot (1.1.8) proxy in front of an old cyrus 2.2.12 and our new
> dovecot server.
> 
>>> Does anybody here have configure a sieve proxy to do this ?
>> Your setup is a bit odd. I haven't tried this ever and doubt anyone else
>> has. The proxying feature is mainly implemented with Dovecot back-ends
>> in mind. In an ideal world this should work however, so there is a
>> possibility that the Dovecot proxy is not working properly.
>>
>>> Or is it a normal behavior and dovecot sieve proxy can't speak with
>>> cyrus sieve ?
>> Theoretically, this setup should be possible. However, the protocol
>> specification is unfortunately not always followed to the letter. Also,
>> Cyrus possibly does not allow you to login with the SASL PLAIN mechanism
>> (the only one supported for proxying now). This seems unlikely though,
>> since the IMAP proxy does work.
> I think you've right, I've done some tcpdump and don't see a lot of
> thing but there is some data on the 2000 port of my cyrus server. But I
> realy wonder if the SASL PLAIN mechanism is the key of the problem ?
> 
> telnet imap-serv sieve
> Trying 138.XX.XX.XX...
> Connected to imap-serv.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v2.2.12"
> "SASL" "PLAIN"
> "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
> relational comparator-i;ascii-numeric regex"
> "STARTTLS"
> OK
> 
> If I configure my remote squirrelmail to directly access to my cyrus
> server, it works ! But as soon as I plug squirrelmail on the proxy it's
> crashing ...
> 
> Thank you for your help
> 
>> Without more information I can only guess what is going on. Could you
>> sniff the communication between Dovecot and Cyrus (e.g. using ngrep)?
>> Perhaps, if it is not too much trouble, I can make it work...
>>
>> Regards,
>>
>> Stephan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mathieu_kretchner.vcf
Type: text/x-vcard
Size: 258 bytes
Desc: not available
Url : http://dovecot.org/pipermail/dovecot/attachments/20090127/bb4dc44e/attachment.vcf