Hi i got nearly the same problem.I can auth against POP and IMAP but not against sieveshell when i try i allways get:
Dec 10 11:55:42 mail timsieved[6167]: cross-realm login [EMAIL PROTECTED] denied Dec 10 11:55:42 mail perl: No worthy mechs found in my auth.log and: Dec 10 11:58:34 mail master[6192]: about to exec /usr/cyrus/bin/timsieved Dec 10 11:58:34 mail sieve[6192]: executed Dec 10 11:58:34 mail sieve[6192]: accepted connection Dec 10 11:58:39 mail timsieved[6192]: badlogin: localhost[::ffff:127.0.0.1] PLAIN authentication failure Dec 10 11:58:39 mail master[946]: process 6192 exited, status 0 in my imapd.log sieveshells itself tells me: mail / # sieveshell [EMAIL PROTECTED] [EMAIL PROTECTED] localhost connecting to localhost Please enter your password: unable to connect to server at /usr/bin/sieveshell line 174, <STDIN> line 1. I use PAM with Mysql as backend an a patched pam_mysql.so module.I have a configuration for each sieve,pop and imap in my /etc/pam.d Does somebody know what this problem cause? Greets Kevin Moschallski Am Mit, den 10.12.2003 schrieb Igor Brezac um 02:38: > On Tue, 9 Dec 2003, Marc G. Fournier wrote: > > > On Tue, 9 Dec 2003, Ken Murchison wrote: > > > > > Marc G. Fournier wrote: > > > > > > > When trying to connect to sieve using sieveshell, using the same > > > > userid/passwd that I've verified does work with IMAP, I'm getting the > > > > following in the log file(s): > > > > > > > > Dec 9 20:28:24 xxxxxx sieve[28283]: no secret in database > > > > Dec 9 20:28:33 xxxxxx sieve[28304]: no secret in database > > > > Dec 9 20:28:36 xxxxxx sieve[28304]: Password verification failed > > > > Dec 9 20:29:01 xxxxxx sieve[28336]: no secret in database > > > > Dec 9 20:29:03 xxxxxx sieve[28336]: Password verification failed > > > > > > > > don't they use the same authentication method(s)? > > > > > > Yes, but sieveshell will try to use the most secure SASL mech offered. > > > So if timsieved offers anything other than PLAIN, you need to have the > > > users secret in an auxprop plugin. If you telnet to the sieve port, > > > what mechs are offered. > > > > "IMPLEMENTATION" "Cyrus timsieved v2.2.2-BETA" > > "SASL" "PLAIN LOGIN DIGEST-MD5 CRAM-MD5" > > > > > Alternatively, if you're only offering plaintext mechs and using PAM, > > > make sure you have a PAM config for the "sieve" service. > > > > Note that I'm using virtdomains, maybe sieveshell isn't compatible for it? > > > > I use virtdomains and it is working fine for me.
