[Dovecot] dovecont.conf and "Evolution Mail" configuration

[Brian G. Peterson]

On Friday 24 November 2006 12:51, maria.freixes_graells at alcatel.es wrote:
> Any idea with the logs? I'm sorry but I understand nothing about
> them...... Another time, thanks to all that help me, sincerently,
> Maria
>
> The logs:
>
> Messages File:
>
> Nov 25 02:13:00 sewebt passwd(pam_unix)[4726]: password changed for
> pepe Nov 25 02:14:22 sewebt su(pam_unix)[4731]: session opened for user
> pepe by root(
> uid=0)
> Nov 25 02:14:26 sewebt su(pam_unix)[4731]: session closed for user pepe
> Nov 25 02:14:54 sewebt dovecot-auth: PAM (dovecot) illegal module type:
> passdb
> Nov 25 02:14:54 sewebt dovecot-auth: PAM pam_parse: expecting return
> value; [... pam]
> Nov 25 02:14:54 sewebt dovecot-auth: PAM unable to
> dlopen(/lib/security/{) 
> Nov 25 02:14:54 sewebt dovecot-auth: PAM 
> [dlerror: /lib/security/{: cannot open
> shared object file: No such file or directory]
> Nov 25 02:14:54 sewebt dovecot-auth: PAM adding faulty module:
> /lib/security/{
> Nov 25 02:14:54 sewebt dovecot-auth: PAM (dovecot) illegal module type:
> args Nov 25 02:14:54 sewebt dovecot-auth: PAM pam_parse: expecting
> return value; [...
> =]
> Nov 25 02:14:54 sewebt dovecot-auth: PAM unable to
> dlopen(/lib/security/*) Nov 25 02:14:54 sewebt dovecot-auth: PAM
> [dlerror: /lib/security/*: cannot open
> shared object file: No such file or directory]
> Nov 25 02:14:54 sewebt dovecot-auth: PAM adding faulty module:
> /lib/security/*
> Nov 25 02:14:54 sewebt dovecot-auth: PAM (dovecot) illegal module type:
> }

Have you searched for these errors online or on the dovecot site?

I notice in your configuration (earlier message) that you have passdb pam 
enabled, but that you don't have any directives uncommented inside your 
passdb pam section.

I see in my config:

 # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM
 # authentication to actually work.
  passdb pam {
    args = "*"
  }

I don't know if this will work for your config.  You need to look up the 
errors, and see what you can find.

The most relevant parts of your error log appear to be

illegal module type: passdb

PAM adding faulty module: /lib/security/{

but I'm just guessing that these are related to your root cause.

Regards,

  - Brian