[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[pysieved] Authentication problem
- From: Matthias Berndt <matthias_berndt at gmx dot de>
- Subject: [pysieved] Authentication problem
- Date: Thu, 19 Jul 2007 18:03:46 +0200
Hi,
I want to use pysieved with dovecot. Authentication is usually done
via GSSAPI (Kerberos, that is). Dovecot is configured accordingly and
provides the auth socket in /var/spool/postfix/private/auth. Postfix
successfully uses that socket for authentication, so it should be OK.
However, when I try to manage my sieve scripts (with kmail), it tells
me NO "Unsupported authentication mechanism"is not supported.
My configuration file looks like this:
[main]
auth = Dovecot
userdb = Virtual
storage = Dovecot
port = 2000
pidfile = /var/run/pysieved.pid
[Virtual]
base = /var/dovecot/
uid = -1
gid = -1
hostdirs = False
[Dovecot]
mux = /var/spool/postfix/private/auth
sievec = /usr/lib/dovecot/sievec
scripts = .dovecot.sieve[PAM]
[PAM]
service = dovecot
I've also tried to do authentication via PAM (via pam_krb5.so). My
dovecot server is configured to support that anyway, so I just told
pysieved to use dovecot's PAM configuration, but when I try to access
the scripts via kmail, it tells me that my user name and/or password
aren't correct (needless to say they are correct, since kmail is able
to fetch my mails with them).
<rant>The fact that pysieved hardly provides any logging at all
doesn't make it easier to debug the configuration. IMO, that is an
absolutely critical feature, and you really shouldn't release a 1.0
without good support for logging facilities. </rant>
Regards
Matthias Berndt