This is the second beta version of the upcoming ISPConfig 3.0.1.4 release. Several bugs from the first beta has been fixed. Changelog ------------------------------------ http://bugtracker.ispconfig.org/index.php?string=&project=3&due[]=27&status[]=closed&do=index New Installation ------------------------------------ Execute the following commands as root user on the shell: Code: cd /tmp wget http://www.ispconfig.org/downloads/ISPConfig-3.0.1.4-beta-2.tar.gz tar xvfz ISPConfig-3.0.1.4-beta-2.tar.gz cd ispconfig3_install/install/ php -q install.php cd /tmp/ rm -rf ispconfig3_install rm -f ISPConfig-3.0.1.4-beta-2.tar.gz Update of an existing ISPConfig installation Installation ------------------------------------ Execute the following commands as root user on the shell: Code: cd /tmp wget http://www.ispconfig.org/downloads/ISPConfig-3.0.1.4-beta-2.tar.gz tar xvfz ISPConfig-3.0.1.4-beta-2.tar.gz cd ispconfig3_install/install/ php -q update.php cd /tmp/ rm -rf ispconfig3_install rm -f ISPConfig-3.0.1.4-beta-2.tar.gz
Web-Server: offline @ ISPConfig-3.0.1.4-beta-2 at Centos 5.3 Update of an existing ISPConfig installation Installation ------------------------------------ Execute the following commands as root user on the shell: Code: cd /tmp wget http://www.ispconfig.org/downloads/ISPConfig-3.0.1.4-beta-2.tar.gz tar xvfz ISPConfig-3.0.1.4-beta-2.tar.gz cd ispconfig3_install/install/ php -q update.php cd /tmp/ rm -rf ispconfig3_install rm -f ISPConfig-3.0.1.4-beta-2.tar.gz [/QUOTE] after the update the Web-server appears offline @ 192.168.0.100:8080 and there is no way to make it go online at the ISPConfig panel. Every time I restart the Apache server it starts ok with out complains! I have checked the httpd and the sys logs but there is no errors! Any clues where to check??? Thanks Carlos Barrera
run: apache2 -t to test it. Did you made any custom modifications to the prior installation like amking port 8080 available via ssl?
Then you have most likely a problem with the customisations you made to the ispconfig configuration to enable ssh and you might have to redo them.
Changes in .mailfilter broked maildrop delivery Hello! I'm not an expert, so I filled a lot of days to solve this little problem. update.php changed /var/vmail/.mailfilter: LOGNAME=tolower("$LOGNAME") EXTENSION="$1" RECIPIENT=tolower("$2") USER=("$3") HOST=("$4") SENDER="$5" DEFAULT="/var/vmail/$HOST/$USER/." to LOGNAME=tolower("$LOGNAME") EXTENSION="$1" RECIPIENT=tolower("$2") USER=tolower("$3") HOST=tolower("$4") SENDER="$5" DEFAULT="/var/vmail/$HOST/$USER/." I don't know why, but maildrop doesn't liked this: "(temporary failure. Command output: /usr/bin/maildrop: Unable to open mailbox. )" After a lot of comparisons, I removed "tolower" from USER and HOST and voilà! Maildrop stands to life! I just wanna know if it is a trick of my Fedora 10 or some else more complicated... Márcio Arnaldo Borges
The problem is when you remove tolower and someone sends an email to e.g. [email protected] instead of [email protected], you will never receive the email as the email is then stored into a new mailbox which starts with a capitalized I. The problem might be that you use a mailbox with a capitalized letter in the mailbox name which was possible to create by a bug in older versions.
Thank you, Till. I checked all of my mailboxes, but none of them have capitalized letters in it. Despite this, all of the maildrop delivery were fail until I changed it. See: Aug 31 09:12:53 sadium postfix/pipe[31032]: B1AC77780DA: to=<[email protected]>, orig_to=<[email protected]>, relay=maildrop, delay=153555, delays=153 Aug 31 09:12:53 sadium maildrop[31847]: Unable to open mailbox. Aug 31 09:12:53 sadium postfix/pipe[30980]: B7D45778119: to=<[email protected]>, orig_to=<[email protected]>, relay=maildrop, delay=9623, delays=962 Aug 31 09:12:53 sadium maildrop[31853]: Unable to open mailbox. Aug 31 09:12:53 sadium postfix/pipe[30989]: B26177780A3: to=<[email protected]>, orig_to=<[email protected]>, relay=maildrop, delay=260668, delays=26 Aug 31 09:12:53 sadium maildrop[31859]: Unable to open mailbox. Aug 31 09:12:53 sadium postfix/pipe[31032]: F423E77811C: to=<[email protected]>, orig_to=<[email protected]>, relay=maildrop, delay=6891, delays=6887 Aug 31 09:13:02 sadium maildrop[31905]: Unable to open mailbox. Márcio
Please check the directory names in: /var/vmail and /var/vmail/xxx.com if any of them are capitalized.
Till, "xxx" stands for any of my domains. And NO: I have no capitalized names into /var/vmail nor /var/vmail/any_of_my_domains. The fail just started after the update from ISPConfig 3.0.1.3 to 3.0.1.4 Beta 2. Márcio
Looks as if there is some kind of bug in maildrop when compiled with specific gcc options which might cause this: http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/842ac6e476d39246 I will try to find a workaround for this.
No, at least not in ISPConfig. Every default installation of apache is listening on 127.0.0.1, so if your dont do that, it must have ben reconfigured to not listen on 127.0.0.1.
Hi 2 ALL Is this a final version or still is beta 2? Regards P.S. Link from http://ispconfig.org/news.htm (2009-09-03 ISPConfig 3.0.1.4 final released) send me to download ISPConfig-3.0.1.4-beta-2.tar.gz.
Sorry, there was a wrong link in the news. The final version is here: http://www.howtoforge.com/forums/showthread.php?t=38795 or just go to downloads on ispconfig.org.