sieve and frontends

[Patrick H Radtke]

I forgot that I had been applying a starttls patch to the src.
Those tls options aren't in the normal release.

I'll just take a look through the patch when I have time to see what needs 
fixing in a tls referral.

thanks,

Patrick

On Sun, 10 Jul 2005, Patrick H Radtke wrote:

> Hey Ken,
>
> I found that things worked with sieve shell when I allowed plain text
> logins on both the backend and the frontend, and when I rain sieveshell
> with --notls.
>
> example:
> sieveshell -u tc2154c -a tc2154c --notls tofu
> connecting to tofu
> Use of uninitialized value in subroutine entry at /usr/bin/sieveshell line 
> 173.
> Please enter your password:
>> list
> Please enter your password:
> ingo  <- active script
>> 
>
> As for the protcol logs.
> Client to frontend is the same for both tls/notls
> ---------- tc2154c Sun Jul 10 16:50:24 2005
>
> <1121028625<LISTSCRIPTS
>> 1121028625>BYE (REFERRAL "sieve://bacon.cc.columbia.edu") "Try Remote."
>
>
> For client to backend, the log only appears with the --notls option
>
> ---------- tc2154c Sun Jul 10 16:51:17 2005
>
> <1121028677<LISTSCRIPTS
>> 1121028677>"ingo" ACTIVE
> OK
> <1121028682<LOGOUT>1121028682>OK "Logout Complete"
>
>
> I don't see anything wrong with the protocol but I'm guessing its a tls 
> issue.
>
> Now that I'm paying more attention, I may have the Cyrus perl libs from 2.3 
> on my machine (I've been doing lots of cvs testing) since I don't think the 
> 2.2.12 release of sieveshell had tls support (I could be wrong though)
>
> -Patrick
>
>
> On Sat, 9 Jul 2005, Ken Murchison wrote:
>
>> Patrick Radtke wrote:
>> 
>>> I'm trying to test our frontends.
>>> 
>>> They work with imap and pop transactions, but if I connected to a 
>>> frontend to use sieve I get an error.
>>> 
>>> sieveshell -u phr2101 -a phr2101 -t "" frontend
>>> connecting to tofu
>>> verify error:num=19:self signed certificate in certificate chain
>>> Please enter your password:
>>>  > list
>>> Bad protocol from MANAGESIEVE server: lost connection
>>> 
>>> 
>>> We have allowplaintextlogins to be off.
>>> 
>>> 
>>> Anyone know what would cause this?
>> 
>> Can you get a protocol trace from both client->frontend and 
>> frontend->backend?
>> 
>> 
>> -- 
>> Kenneth Murchison     Oceana Matrix Ltd.
>> Software Engineer     21 Princeton Place
>> 716-662-8973 x26      Orchard Park, NY 14127
>> --PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp
>> 
> ---
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html