Yes i got the logs on the backend.... it's something with ssl or some other authoption... i will debug, i think it's ssl or plaintext errors and if i'm right cyrus do not take plaintext on the backends if not using ssl.. and without ssl i must use digest or kerberos. i will try what you are telling me to do and report when done. thanks! /C Den Må, 2006-10-16, 18:58 skrev Alexandros Vellis: > On Mon, 2006-10-16 at 18:43 +0200, Casper wrote: > >> Yes i have tested, i must play a little with the plugincode. >> I let the users login with user@xxxxxxxx on the proxy/frontends but the >> backends just have cyrus and proxycyrus users setup, no @domain.tld auth >> as the frontends/proxy. > >> So the proxyserver and avelsieve does not work well here in this (my) >> enviroment (i use 2.3.7 no cvs). > > > Do the server logs on the backend say anything about sieve? If you are > using PHP5, then avelsieve might try to use STARTTLS for the Sieve > connection. However, your cyrus server might not be configured for this. > I'm rolling out a version that will allow to disable STARTTLS for the > people who don't want it. > > I see that the proxy feature for sieve is there since 2.3.6: > > > * Added sieve_allowreferrals option to control whether timsieved > issues referrals or proxys traffic to backends. > > Can you experiment a bit with this option, to see if this solves the > matter for you? > > > Also can you enable AVELSIEVE_DEBUG per manual? (see > http://email.uoa.gr/projects/squirrelmail/avelsieve_reportingbugs.php ) > It should display at least the server it is connecting to, the > username/password, and probably the error message... > > > >> So if i read the manual right, the avelsiev should connect to the same >> imapproxy/frontend as all other clients (like the webmail) and then be >> redirected to the right backend.... > > Yes. > > > The difference with Squirrelmail IMAP code is that avelsieve will _do_ > follow the referral, rather than let the frontend do the job. > > So if you are restricting access from the webmail machine to the > backend's sieve port, you might have trouble. > > Can you check, on the webmail machine, if you can do 'telnet > backend1.example.org 2000' ? > > Also if you have sieveshell on there, you can use that to try and see if > the connection succeeds. > > > P.S. Sorry for the long email. :) Try everything I suggest top-down and > let me know. > > > -- > Alexandros Vellis > avel@xxxxxxxxxx > > > > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users