On Fri, 24 Nov 2006, Brian G. Peterson wrote:

On Friday 24 November 2006 09:34, maria.freixes_graells@alcatel.es wrote:

...

...

Please....I am lost completly!! Could anyone help me to solve the question of how can I configure the mail in my linux machine.... The scenarious is that this linux machine with red had enterprise linux 4 receives mail from another machine via sendmail. This mail is saved into /var/spool/mail/ directori, the user is webmaster. But I want that the mails into /var/spool/mail/webmaster are sended to the "evolution mail" via pop protocol. Any idea? If you could weaste some time with me, I be very gratefully for it!! Thanks a lot, Maria

maria.freixes_graells@alcatel.es escribió:

...

Hello people!!

First, thanks very much to Ejay Hire and to John Peacock for your quickly answer!!

Now, I've dovecot installed, I downloaded the source and I compiled them. It's running ok now.

But.....as I am new in all these issues I have some problems with the configuration.

I have a user called "webmaster" that have a mail into /var/spool/mail, I want to redirect these mails to the "Evolution Mail" program from my Linux Desktop. I have doubts in two ways:

1.- Is the dovecot.conf file correct? 2.- Are the "Evolution Mail" setting correct?

Evolution Account Settings: Name: webmaster@bar.ses.alcatel.es Full Name: webmaster Email Address: webmaster@bar.ses.alcatel.es Server Type: POP Host: 159.23.98.66 Username: webmaster Server Type: SMTP Server Configuration: 159.23.98.66

You need to have an uncommented "protocol pop3" section in your config file. There are many examples both in the comments in the distributed dovecot.conf file, and on the dovecot website.

for example:

protocol pop3 { listen = *:110 }

would listen on the standard pop3 port (110) for connections from all hosts.

protocol pop3 { listen = localhost:110 } would listen only on localhost (the same machine, not allowing any remote connections to dovecot)

Or, on my server, I use: protocol pop3 { ssl_listen = *:995 } allowing only encrypted connections to pop3 from anywhere.

you could also combine directives like this:

protocol pop3 { listen = *:110 ssl_listen = *:995 }

I have never uncommented, no modified any of those settings, yet I can connect just fine using STARTTLS. I did make sure that I had both IMAPS and POP3S listed under 'protocols' however.

-- Gerard gerard@seibercom.net

Recursion: n. See Recursion.

Random Shack Data Processing Dictionary

On Friday 24 November 2006 12:20, maria.freixes_graells@alcatel.es wrote:

root@sewebt home]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK Dovecot ready. user pepe +OK pass pepe06 -ERR Temporary authentication failure. Connection closed by foreign host. [root@sewebt home]#

It fails!! Some problem with the 110 port?

Check the dovecot log. Authentication errors at the client side are deliberately vague for security reasons. The actual reason for your failure to authenticate will be in the server mail logs.

Check /var/log/maillog, or look at your syslog config to see where it is going.

Regards,

• Brian

On Friday 24 November 2006 12:51, maria.freixes_graells@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