I recently suffered a catastrophic disk failure on a live server: the live server was running Centos 5.4 and an earlier version of ISPCongfig 3. I had recently made backups of user data and all databases. While the server was having a new disk fitted (very slow support!) I set up a new server by following the perfect server guide for Centos 5.5/x86_64 (with the exception of using mydns in place of bind) I then restored the databases (including dbispconfig) and other data. On running ISPConfig, a few things didn't work: I found that restoring the database had removed some new columns in dbispconfig. I re-added those manually. Everything now appears to work except mail. Any attempt to log in brings up the user/password box. The mail log shows "servername pop3d: LOGIN FAILED, [email protected]," Further up the mail log we have Code: Feb 10 08:20:10 server authdaemond: Installing libauthuserdb Feb 10 08:20:10 server authdaemond: file not found Feb 10 08:20:10 server authdaemond: Installing libauthpam Feb 10 08:20:10 server authdaemond: Installation complete: authpam Feb 10 08:20:10 server authdaemond: Installing libauthpgsql Feb 10 08:20:10 server authdaemond: file not found Feb 10 08:20:10 server authdaemond: Installing libauthldap Feb 10 08:20:10 server authdaemond: file not found Feb 10 08:20:10 server authdaemond: Installing libauthmysql Feb 10 08:20:10 server authdaemond: file not found Feb 10 08:20:10 server authdaemond: Installing libauthcustom Feb 10 08:20:10 server authdaemond: Installation complete: authcustom Feb 10 08:20:10 server authdaemond: Installing libauthpipe Feb 10 08:20:10 server authdaemond: file not found Is that pertinent? It also reports Code: postfix/smtpd[9045]: warning: SASL: Connect to private/auth failed: No such file or directory I am running dovecot and I have confirmed that the dovecot config file contains the correct mysql login details To confuse matters further, during the perfect server install guide it says "(it is ok if you see this error: Starting Mail Virus Scanner (amavisd): Config file "/etc/amavisd/amavisd.conf" does not exist, at /usr/sbin/amavisd line 1795. - the missing configuration file /etc/amavisd/amavisd.conf will be created by the ISPConfig installer.)" However after ISPConfig has been installed amavisd will not start giving the error "Config file "/etc/amavisd/amavisd.conf" does not exist"
download ispconfig tar.gz and run the ispconfig update.php script. Choose to reconfigure services during update.
Thanks for the suggestion. I've done that but it hasn't helped. I think I'll try and rebuild the server from scratch again, then with a fresh installation of ISPConfig, test the mail service. If that works, I'll reinstall the dbispconfig from my backups, run updatephp and see if it still works. So I'll be reporting back in a few hours . (In fact I've got four servers with ISPConfig installed - server one is serving HTTPD for my clients while I try and sort out the email problem. Email service is currently transfered to another server running DirectAdmin. It is server two that I will be rebuilding now. It takes 1hr 10minutes to reformat and reinstall Centos - then I reorganise the partitions and upgrade Centos to 5.5 - then run the perfect server guide.)
Stage 1: Server rebuild complete.... and ISPConfig freshly installed. The mail system works correctly except amavisd. If I attempt a restart, it still comes up with the message: 'Config file "/etc/amavisd/amavisd.conf" does not exist' MyDNS, however does not work. The mydns config file has not been updated by the ISPConfig installer, so I've had to manually edit the file. FIXED. Bind was preinstalled. The installer runs 'which' to discover which services are installed. If it finds bind (ie named) it configures bind and then doesn't bother with mydns. So by uninstalling bind, I've forced ISPConfig to configure mydns for me. I might have a go at submitting a patch so that the installer will alert the user if there is more than one alternative for any particular servcie and allow the user to choose which to use. (also useful for courier v. dovecot)
err.... actually the mail system wasn't working properly, but it didn't have any login problems. I had to create a symbolic ink from /etc/amavisd.conf to /etc/amavisd/amavisd.conf to make amavis work. [Why does the Perfect server guide instruct us to use a non-standard location for the conf file?] Then the mails came tumbling through. (I am updating on my progress on here so that anyone else suffering similar problems can learn from my mistakes!)
Having had a conflict between MyDNS and BIND when rebuilding server two, I decided to re-evaluate services running on server one (live server). I removed courier(-map,-authlib) and installed dovecot/dovecot seive in its place then ran ispconfig's update script and mail seems to be working again.
Do not do this on a mailserver that conatains already mailboxes, as all email and mail filter rules that have been created before become inaccessible. courier and dovecot use a different mailfolder layout.
