Hi guys! I'm new to ISPConfig. Everything works fine exept two things: 1. I can't auth for sending mail through smtp, why? (imap runs perfect) 2. I can creat only 1 web with ssl support. It doesn't make sens to me. Can somebody help me out? thanks!
I am new to ISPConfig as well and I have my own set of problems I am trying to work out. I have no clue to your first question, but I might be able to help you with you second one. I believe you need a unique virtual IP for each site you want to run with SSL. In order to do that you need to enter the virtual IP numbers in the list located under the settings menu in the ISPConfig control panel. But before you do that you can modify your config.inc.php file. --------------- The automatic network configuration is disabled by default. Edit the /home/admispconfig/ispconfig/config.inc.php file and set: $go_info["server"]["network_config"] = 0; // 0 = none, 1 = automatic to: $go_info["server"]["network_config"] = 1; // 0 = none, 1 = automatic --------------- Then reboot --------------- Here is the link that i found the info under http://www.howtoforge.com/forums/sh...ighlight=$go_info["server"]["network_config"] -------------- I hope this helps Bill
IMAP has nothing to do with SMTP authentication. Which errors do you get in your mail logfile, when you try to authenticate over smtp? Its a limitation of the SSL protocol, not of ISPConfig. Please read this explanation: http://www.howtoforge.com/forums/showthread.php?t=9605
Hi Til and bfriend! I fixed the ssl - limitation as described. Thanks! ad 2: SMTP auth Problem (I know that imap != smtp but i thought it would be a helpfull information) here ist the output of the log: Code: Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: no secret in databas e Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL CRAM-MD5 au thentication failed Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: no secret in databas e Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL NTLM authen tication failed Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 last message repeated 4 times Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: Password verificatio n failed Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL PLAIN authe ntication failed Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:56 linux1 last message repeated 5 times Jan 6 16:51:56 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL LOGIN authe ntication failed Jan 6 16:51:59 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:51:59 linux1 last message repeated 2 times Jan 6 16:51:59 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: no secret in databas e Jan 6 16:51:59 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL CRAM-MD5 au thentication failed Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:52:00 linux1 last message repeated 2 times Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: no secret in databas e Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL NTLM authen tication failed Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:52:00 linux1 last message repeated 5 times Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: SASL authentication failure: Password verificatio n failed Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL PLAIN authe ntication failed Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: SASL authentication problem: unable to open Berke ley db /etc/sasldb2: No such file or directory Jan 6 16:52:00 linux1 last message repeated 5 times Jan 6 16:52:00 linux1 postfix/smtpd[4381]: warning: virus.hpserver.id[192.168.0.20]: SASL LOGIN authe ntication failed bdb errors
ISPConfig does not use the DBD authentication from SASL at all, so I guess your SASL is not configured correctly to aurhenticate against PAM. Did you follow one of the perfect setup guides?
Then please redo the sasl authentication steps and check that you dont have any typos in the config files. Which linux distribution do you use and is this a 32 or 64Bit linux?
It's a 32bit debian 3.1 sarge. After a look at the config of saslauthd it was everything as described, but u said sasl should not use PAM (and PAM uses BDB). This is out of the Howto http://www.howtoforge.com/perfect_setup_debian_sarge_p4 May the last line be the problem?
ok. I got no /etc/postfix/sasl/smtpd.conf ... only /etc/postfix/sasl/smtpd.config ... Code: pwcheck_method: saslauthd mech_list: plain login
