cannot authenticate to Sieve

Andreas Winkelmann ml at awinkelmann.de
Thu Sep 21 15:58:36 EDT 2006


Am Thursday 21 September 2006 20:43 schrieb Jean-Gabriel Duquesnoy:

> > > I have been following several threads concerning similar issues,
> > > but could not find the information which would have helped me
> > > solve the issue I am encountering. When using sivtest as follows:
> > > mail:/var/log # sivtest -a duke -u duke 192.168.0.5
> > > S: "IMPLEMENTATION" "Cyrus timsieved v2.2.12"
> > > S: "SASL" "PLAIN"
> > > S: "SIEVE" "fileinto reject envelope vacation imapflags notify
> > > subaddress relational comparator-i;ascii-numeric regex"
> > > S: OK
> > > Please enter your password:
> > > C: AUTHENTICATE "PLAIN" {24+}
> > > ZHVrZQBkdWtlAFNwb29reTc=
> > > S: NO "Authentication Error"
> > > Authentication failed. generic failure
> > > Security strength factor: 0
> > >
> > > in the logfile I found the following:
> > >
> > >  Sep 19 20:14:40 mail master[11029]: about to
> > > exec /usr/lib/cyrus/bin/timsieved
> > > Sep 19 20:14:40 mail sieve[11029]: executed
> > >
> > > Sep 19 20:14:40 mail sieve[11029]: sql_select option missing
> > > Sep 19 20:14:40 mail sieve[11029]: auxpropfunc error no mechanism
> > > available
> > > Sep 19 20:14:40 mail sieve[11029]: _sasl_plugin_load failed on
> > > sasl_auxprop_plug_init for plugin: sql
> >
> > You have installed the sql-Auxprop Plugin. Either Deinstall it, or
> > use a "sasl_sql_select: dummy" in your imapd.conf.
> >
> > > Sep 19 20:14:40 mail sieve[11029]: accepted connection
> > > Sep 19 20:14:44 mail sieve[11029]: could not find auxprop plugin,
> > > was searching for '[all]'
> >
> > Show your imapd.conf.
>
> postmaster: postmaster
> configdirectory: /var/lib/imap
> partition-default: /var/spool/imap
> sievedir: /var/lib/sieve
> admins: cyrus
> allowanonymouslogin: no
> allowplaintext: yes
> sasl_mech_list: PLAIN
> servername: servername.domainname.com
> autocreatequota: 10000
> reject8bit: no
> quotawarn: 90
> timeout: 30
> poptimeout: 10
> dracinterval: 0
> drachost: 127.0.0.1
> sasl_pwcheck_method: saslauthd
> #sasl_pwcheck_method: auxprop
> lmtp_overquota_perm_failure: no
> lmtp_downcase_rcpt: yes
> sendmail: /usr/sbin/sendmail
> sieve_maxscriptsize: 32
> sieve_maxscripts: 5
> sieve_sasl_minimum_layer: 0

> sasl_minimum_layer: 1

sasl_minimum_layer above 0 without Configuring ssl/tls?
Change this.

> autocreateinboxfolders: INBOX | INBOX.Trash | INBOX.Sent |
> INBOX.Drafts
> autosubscribeinboxfolders: INBOX | INBOX.Trash | INBOX.Sent |
> INBOX.Drafts
>
> #
> # if you want TLS, you have to generate certificates and keys
> #
> #tls_cert_file: /usr/ssl/certs/cert.pem
> #tls_cert_file: /etc/certs/imapd.pem
> #tls_key_file: /usr/ssl/certs/skey.pem
> #tls_ca_file: /usr/ssl/CA/CAcert.pem
> #tls_ca_path: /usr/ssl/CA
>
> > > Sep 19 20:14:44 mail saslauthd[4028]: pam_mysql - MySQL error
> > > (Can't connect to local MySQL server through socket
> > > '/var/lib/mysql/mysql.soc
> > > k' (2))
> >
> > Is the MySQL Server running? Is the Path to the Socket
> > (/var/lib/mysql/mysql.sock) correct? What is with the Permissions?
> > Is Cyrus-Imapd able to reach it?
>
> The path is a different one, but where do I set this for sieve? Imap,

Edit your .../pam.d/sieve and change the host-Argument in the pam_mysql 
Options to "... host=/var/lib/mysql/mysql.sock ...".

> Potsfix, Cyrus and eGroupware are able to access the MySQL database.

Where do you see the difference between "Cyrus", "Imap" and "Sieve"?

> > > Sep 19 20:14:44 mail saslauthd[4028]: pam_unix_auth(sieve:auth):
> > > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
> > > user=duk
> > > e
> > > Sep 19 20:14:46 mail saslauthd[4028]: DEBUG: auth_pam:
> > > pam_authenticate failed: Permission denied
> > > Sep 19 20:14:46 mail saslauthd[4028]: do_auth         : auth
> > > failure: [user=duke] [service=sieve] [realm=jgduke.dnsalias.com]
> > > [mech=pam] [r eason=PAM auth error]
> > >
> > > Sep 19 20:14:46 mail sieve[11029]: Password verification failed
> > > Sep 19 20:14:46 mail sieve[11029]: badlogin:
> > > mail.jgduke.dnsalias.com[192.168.0.5] PLAIN authentication
> > > failure Sep 19 20:14:53 mail master[15260]: process 11029 exited,
> > > status 0 Sep 19 20:15:50 mail kernel: SFW2-INext-DROP-DEFLT
> > > IN=eth0 OUT= MAC= SRC=192.168.0.5 DST=192.168.0.255 LEN=78
> > > TOS=0x00 PREC=0x00 TTL=64 ID=
> > > 0 DF PROTO=UDP SPT=137 DPT=137 LEN=58
> > > Sep 19 20:15:54 mail last message repeated 3 times
> > > Sep 19 20:15:55 mail kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT=
> > > MAC= SRC=192.168.0.5 DST=192.168.0.255 LEN=211 TOS=0x00 PREC=0x00
> > > TTL=64 ID
> > > =0 DF PROTO=UDP SPT=138 DPT=138 LEN=191
> > > Sep 19 20:16:13 mail master[11056]: about to
> > > exec /usr/lib/cyrus/bin/timsieved
> > > Sep 19 20:16:13 mail sieve[11056]: executed
> > > Sep 19 20:16:13 mail sieve[11056]: sql_select option missing
> > > Sep 19 20:16:13 mail sieve[11056]: auxpropfunc error no mechanism
> > > available
> > > Sep 19 20:16:13 mail sieve[11056]: _sasl_plugin_load failed on
> > > sasl_auxprop_plug_init for plugin: sql
> > > Sep 19 20:16:13 mail sieve[11056]: accepted connection
> > > Sep 19 20:16:18 mail sieve[11056]: could not find auxprop plugin,
> > > was searching for '[all]'
> > > Sep 19 20:16:18 mail saslauthd[4027]: pam_mysql - MySQL error
> > > (Can't connect to local MySQL server through socket
> > > '/var/lib/mysql/mysql.soc
> > > k' (2))
> > > Sep 19 20:16:18 mail saslauthd[4027]: pam_unix_auth(sieve:auth):
> > > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
> > > user=duk
> > > e
> > > Sep 19 20:16:20 mail saslauthd[4027]: DEBUG: auth_pam:
> > > pam_authenticate failed: Permission denied
> > > Sep 19 20:16:20 mail saslauthd[4027]: do_auth         : auth
> > > failure: [user=duke] [service=sieve] [realm=] [mech=pam]
> > > [reason=PAM auth erro r]
> > > Sep 19 20:16:20 mail sieve[11056]: Password verification failed
> > > Sep 19 20:16:20 mail sieve[11056]: badlogin:
> > > mail.jgduke.dnsalias.com[192.168.0.5] PLAIN authentication
> > > failure Sep 19 20:16:35 mail master[15260]: process 11056 exited,
> > > status 0
> > >
> > > Which settings are missing or wrong which could cause this? It
> > > seems some information on how to access the MySQL database is
> > > missing, but I do nto know which.
> > >
> > > Any help would be greatly appreciated.

-- 
	Andreas


More information about the Info-cyrus mailing list