We are opening and making this thread a sticky until upgrades are completed. We are making this BEFORE the email announcement where we will inform of the date of the upgrade, so that we can link to the thread in the announcement. In effect this is currently a placeholder thread.
We’d ask that you keep any upgrade discussion or questions to this thread and not all over the forum. We will be here frequently to answer any questions that may arise in the process. Should you need to have a more direct question that you do not wish to be public, you can start a thread in the customer only section, if there is much demand for customer only discussions we will create and merge topics there to one as well in order to answer all questions and concerns in the most orderly manner.
I appreciate your upgrading to provide new features and better service, but how about upgrading to SQL Server 2005, instead of making it an extra that’s hard to manage. I’ve been with you for a almost year, and I thought surely you would have true 2005 support by now.
Several of my C# .NET 2.0 applications occasionally send multiple e-mails using your SMPT server. Will the e-mail changes you speak of affect these applications.
Re: Will e-mails sent by applications be affected?
Hello,
We will not/can not upgrade the MSSQL Servers, this is a very complex upgrade process and not a recommended. The means used to do such can not work well/properly in a shared environment.
As for mail services, there won’t be any changes that will cause problems there except of course the momentary reboots of windows and mail servers, but this won’t be any change that will require modifications on your part.
I didn’t have in mind upgrading the existing servers, but making SQL 2005 available for new databases using the normal control panel. Surely you don’t plan to support only 2000 forever, with later releases available only on and ad hoc basis.
We can’t change the design of the control panel, if it were up to me all new DBs would go to the new server even for people already having DBs, but this is not the way it works. As it is now any new user or user without SQL databases currently goes to the new SQL 2005 server(mssql10).
I had mentioned that it may work at one point, but upon research it did not, after the upgrade we will see if there is any way to change the target server, it is not too useful to do it now as it will change back.
It should technically work, but it still is remember the old after DBs are gone.
Correct, if we change it now it could cause further complications in the upgrade, it would just be best to do it after and then attempt to delete, change target db and add them back.
(1) what is the reason to disable “catch-all” feature? we have lots of customers who are using “catch-all” feature to run virtual mail servers - please advise?
Catchalls are the cause for much spam and server bounces that cause blacklistings, existing catchalls will work, new will not be available. Use multi aliases instead of catchall.
CFMX7 yes, 8, we are testing but it is not officially supported and has some troubles at the moment, since there will be some delay between the upgrade and the Wincf3 deployment, we are hoping for a development in this time.
“The first phase being the control panel server itself, this will involve the control panel services being completely down for the period of the upgrade. Linux web, mail and VPS services will be updated during this period.”
What does this mean, for how long will linux web, mail and VPS services be down?
The notice does say about the web services: Estimated Webservice downtime is 30 minutes to an hour per Linux webserver.
There shouldn’t be any downtime for mail or VPS as it is going to be a few scripts and packages that will be updated. I’m still going to update the notice and mention a 15 mins of possible service interruption for mail & VPS services, just for any possible issue that hasn’t been seen yet.