I'm getting some errors I wanted to run past you guys... Once logged in to ISPc3 under Monitor Show mail warn log I get Code: Jun 5 09:03:40 sierra postfix/postalias[23325]: warning: /etc/aliases.db: duplicate entry: "root" Jun 5 11:21:15 sierra postfix/postalias[7337]: fatal: open /etc/aliases.db: Permission denied My /etc/aliases file looks like this: Code: #Added by installer for initial user postmaster: root clamav: root root: [email protected] webmaster: root Is that setup not acceptable? If I do Code: sudo newaliases I don't get an error. Under Monitor/mail-log I'm also seeing Code: Jun 5 10:15:01 sierra postfix/smtpd[6336]: disconnect from localhost.localdomain[127.0.0.1] Jun 5 10:20:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1] Jun 5 10:20:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1] Jun 5 10:20:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1] Jun 5 10:20:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0 Jun 5 10:20:01 sierra postfix/smtpd[6389]: connect from localhost.localdomain[127.0.0.1] Jun 5 10:20:01 sierra postfix/smtpd[6389]: lost connection after CONNECT from localhost.localdomain[127.0.0.1] Jun 5 10:20:01 sierra postfix/smtpd[6389]: disconnect from localhost.localdomain[127.0.0.1] Jun 5 10:25:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1] Jun 5 10:25:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0 Jun 5 10:25:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1] Jun 5 10:25:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1] Jun 5 10:25:01 sierra postfix/smtpd[6439]: connect from localhost.localdomain[127.0.0.1] Jun 5 10:25:01 sierra postfix/smtpd[6439]: lost connection after CONNECT from localhost.localdomain[127.0.0.1] Jun 5 10:25:01 sierra postfix/smtpd[6439]: disconnect from localhost.localdomain[127.0.0.1] over and over, logged every five minutes. Presumably not right? I can't find any other refs to this in the forums. Any ideas? S
I guess this means you won't see that error again in ISPConfig. That's ISPConfig's monitoring module which tries to check which services are running and which are not. There's nothing wrong with this.
Falko, Thanks as always... I do still see the error. In fact, since I installed fail2ban and ran the ISPc update I see Code: Jun 5 09:03:40 sierra postfix/postalias[23325]: warning: /etc/aliases.db: duplicate entry: "root" Jun 5 11:21:15 sierra postfix/postalias[7337]: fatal: open /etc/aliases.db: Permission denied Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: SASL authentication failure: Couldn't find mech GSSAPI Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: sierra.myserver.com[192.168.0.55]: SASL GSSAPI authentication failed: no mechanism available 'newaliases' in the terminal still gives no error. I'm assuming these errors are still current, although they are dated yesterday...? Are the additional lines because I haven't configured fail2ban? I was going to follow this: http://www.howtoforge.com/fail2ban_debian_etch ... although I'm on Ubuntu 8.04... S
The aliases db is not part of a ispconfig 3 setup and not managed or changed by ispconfig, so this must have been wrong already before you installed ispconfig. To fix this, just edit the aliases file, remove the duplicate entrys for root and then run the "newaliases" command. ISPConfig supports only plain and ogin as authentication mechanisms. Please reconfigure your mail client to use plain or login for smtp authentication.
Till, Thanks for your reply... So the aliases file above isn't acceptable? Why don't I get an error when I run 'newaliases' in the terminal? The second error only appeared after I installed fail2ban and ran the ISPc update command. I haven't tried to actually use the mailserver by logging in with a client. Could the error have been triggered by the nessus scan I ran? Or by fail2ban? Edit: I seem to be error free by making my aliases file look like this: Code: #Added by installer for initial user postmaster: [email protected] clamav: [email protected] root: [email protected] webmaster: [email protected] Not sure what was wrong with the original setup though... Thanks S
Two hours spent wondering what was wrong with that 'lost connection from localhost' mess ! Once again : it's not a bug, it's a feature ! Thanks for the relief.
