ISPConfig 2.2.40 released

Thank you guys! We always appreciate an update.

On Centos 5.5:

After install, the spamassassin was not updated for some reason and we noticed it was not scanning mail any more after a few hours. The solution was to run the updater:

[root@...]# /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/sa-update

That put it all back right again and it was fully upgraded:
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06)...

THANKS again,

R Bartz

 

Hi
I am running ver 2.2.1 on Mandriva 2008.
Is it ok to upgrade to this release?
Also where can I find upgrade instructions.
Thanks

 

The upgrade should work, but to go sure, make a backup of the ISPConfig database plus the directories /root/ispconfig and /home/admispconfig before.

The upgrade is done exactly like a new installation:

Code:

cd install_ispconfig/
./setup

 

bebe

thanks for tthe updates...

 

Upgrading from 2.2.37

Hi
As it seems I missed some updates. Aren't there Newsletters when new 2.x releases are out? I only got info on updates of 3.x.

But for my question. Is it save to update from 2.2.37 up to 2.2.40 in one step or need I to go to 2.2.38 and 2.2.39 first.

Best regards
Bernd

 

Is there no support for Debian 5.0.9?

 

Yes. But make backups before you do this to be on the safe side.

 

Looks like we have to make a new release with support for 5.0.9...

 

Will it be sufficient just to add the following lines to dist.txt for installation on a Debian 5.0.9?

Or is it a better idea to update Debian to 603 first? What are the entries with debian 609 are for? For releases to come in the future?

 

You also need to adjust the files in the mod subdirectory.

Yes.

 

I had a glance at the changes needed to support Debian 5.09, and it doesn't seem to be simple stuff. Very easy to get something wrong, so I probably won't try it.

Is the possible 2.2.41 coming anytime soon ?

 

Only in case of a security update. Otherwise we focus our efforts on ISPConfig 3.

 

OK, thanks.

I asked the question because you or Till mentioned support for Debien 5.09 in the next release, which I use. But I understand we'll have to wait for a security breach to get this feature ?

 

I guess you can simply add new sections for Debian 5.0.9 to dists.txt and the files in the mod/ subdirectory by simply copying a section of an earlier Debian 5 section.

 

Changed all debian508 occurences with debian509 and it did the trick.

I'm still concerned about trying to manage the domain mentioned here though, because it really turned to a nightmare last time. If you have any ideas about the preventive measures I should take before trying again, or a short hint about what could have happened, it'd be great.

 

Does that mean there is now an upgrade path from ISPConfig 2 to ISPConfig 3?

 

No, you cannot upgrade from 2 to 3.

 

OK. I guess that there will be no features added to 2, and no bugfixes unless they affect security. That's OK by me.

How long will security patches be updated for? Is it still indefinite, or do you have plans to stop at some date?

Moving to a different platform is something I'd want to plan for well in advance!