From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1
Description of problem:
sieveshell cannot be executed eventhough sasl authentification is ok
Version-Release number of selected component (if applicable):
Steps to Reproduce:
install cyrus-imapd and its dependencies
1. open terminal and su -
/usr/sbin/saslauthd -m /var/run/saslauthd -a shadow -d
(this the default startup for saslauthd but with foreground debugging)
2. open second terminal and su -
service cyrus-imapd start
passwd cyrus (use paswd "toto" for example -- confirm)
3. execute "sieveshell --user=cyrus --auth=cyrus localhost"
enter passwd toto
Actual Results: unable to connect to server at /usr/bin/sieveshell line 169, <STDIN> line 1.
Expected Results: a normal login to sieveshell
check the terminal running the saslauthd instance and you will see:
do_auth: auth success: [user=cyrus] [service=sieve] [realm=] [mech=shadow]
that sasl authorized access but that sieveshell bombed -- the same holds true for sivtest.
hope you can help!
sieve server process is broken under rhel 4
can we get some help on this?
Yup, its in the queue, probably will start looking at it this afternoon.
thanks for your note -- i've tried and tried, but have yet to find where it's
although not a programmer, i did do an strace which yeilded little information
on localizing the issue. as stupid as it may sound looking at the error message,
i have hunch that the answer will be found in perl, although i did get a mail
message from another user (experiencing same issue) that indicated that
timsieved binary is reponsible. i'll be testing a prebuilt timsieved this
afternoon and see if that sheds some light.
I've investigated this long time ago. IIRC it turned out that sieveshell doesn't
honor the sasl_mech_list option in /etc/imapd.conf (should it?) and also doesn't
allow one to specify the mech to use with something like --mech=PLAIN. I think
it's not a problem of the timsieved server itself but of the managesieve Perl
Hm, no. Now I remember a bit more. It doesn't make sense to run sieveshell as
user cyrus (or every other user defined as cyrus admin). Running it for a valid
IMAP user like this works well for me:
sieveshell -u user -a user localhost
Unfortunately I'm always slow to remember things...
apologize for the delay --
your comments are quite right -- in principle, user "cyrus" should not receive mail.
well (drum roll please) i found out why:
cyrus sieve requires that the mailbox exist prior to running sieveshell or
sivtest. having the autocreate feature "on" doesn't help.