Gianni Socionovo wrote:
Okay, we're getting closer. Normally saslauthd does not support md5, it only supports plain and login. The example you mentioned also set sasl_mech_list=plain. Though you did mention that Imap was working for you, right?
Yes, you are right.
If you can authenticate to Imap you should be able to authenticate to sieve the same way. I'm starting to believe that auth is not the real problem.
connecting to localhost unable to connect to server at /usr/bin/sieveshell line 169
I would like you to check something...I dimly remember that I had a bit of trouble, too, when I tried to set up sieve. Somewhere in the Smartsieve docs they mentioned that a libmcrypt was needed for sieve to work correctly. what does rpm -qa | grep -i "crypt" gives as result?
my rpm -qa|grep -i "crypt" shows the following packages:
libxcrypt-2.2-2 libgcrypt-1.2.0.-3 php4-mycrypt-4.3.8-8 perl-Crypt-SmbHash-0.02-2 libmcrypt-2.5.7-123
Okay, I have also installed perl-mcrypt. In the meantime I took a closer look at /usr/bin/sieveshell to discover what sieveshell needs to run. It's just a perl script with some required modules. Could you please check if you have these perl modules installed: perl-Authen-SASL-Cyrus-0.11-2 perl-Mcrypt-2.4.8.2-468 perl-Authen-SASL-2.08-2 perl-TermReadKey-2.21-294 perl-Digest-SHA1-2.10-2 perl-IO-stringy-2.109-29 perl-Cyrus-SIEVE-managesieve-2.2.8-6 Especially the last module is needed to run sieveshell. Sandy