sieveshell connection fails, while imap works ... ?

[Ken Murchison]

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.

Alternatively, if you're only offering plaintext mechs and using PAM, 
make sure you have a PAM config for the "sieve" service.

-- 
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