After a bad shutdown (power outage) my ISPConfig will no longer allow smtp with SASL. This was in the mail.log file: I tried to start saslauthd and the system responded it was already running. When I test the connection using "telnet localhost 25" I get this: Code: ehlo localhost 250-[host].[domain].com 250-PIPELINING 250-SIZE 20480000 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH LOGIN PLAIN 250-AUTH=LOGIN PLAIN 250 8BITMIME 250-STARTTLS 502 Error: command not implemented What should I be looking for at this point?
Apparently you are missing more than one important file due to the power failure. There is very little hope to recover from this without a re-install as it's very hard to figure out which files are either missing or corrupt. You might give the directories 'lost+found' (per filesystem) a look to see if you find recognizable contents (The files are just numbered files, no names anymore), but I advise a re-installation. Power failures are the most unwanted events for Linux, because lots of things are cached. A UPS is advisable......
I have walked through the configuration steps from "The Perfect Debian Sarge Setup) and found nothing wrong from that viewpoint. I also looked in lost+found and there was nothing. Assuming that some random file was damaged in the power outage, would it be harmful to actually go through the steps in "The Perfect" section for Postfix? Code: Postfix/POP3/IMAP In order to install Postfix with SMTP-AUTH and TLS as well as a POP3 server that also does POP3s (port 995) and an IMAP server that is also capable of IMAPs (port 993) do the following steps: apt-get install postfix postfix-tls libsasl2 sasl2-bin libsasl2-modules ipopd-ssl uw-imapd-ssl (1 line!) Or are there better directions to go?
As the error is SASL related, I'd then try to only reinstall SASL Code: apt-get install libsasl2 sasl2-bin libsasl2-modules and do the appropriate configuration steps for SASL.
