Upgrading WebMail |
The following covers how to upgrade WebMail. There are a number of ways to
upgrade WebMail and these are explained in the sections below.
If you have any questions, or need to know more about any aspect of WebMail, please Email: |
Basic Upgrade |
There are 2 simple ways to do a basic upgrade of WebMail.
They are explained below. SurgeMail Distribution
WebMail Distribution
|
Upgrading the CGI only |
If you wish to only upgrade the CGI and would like to do it by hand all you need to do is rename the OLD cgi so that you have a backup, just in case you wish to move back to the old version. Then copy over the webmail CGI. The CGI will be located in the 'cgi-bin' or 'scripts' folder of the web server. The file might have a extension of .cgi or .exe depending on the setup. In this sort of case I expect the CGI is provided by Netwin support. But you can do this from the SurgeMail and WebMail distribution, you will just need to extract the CGI from the download. |
Adding New Templates |
If you have upgraded your site with a new version of webmail which has templates that you did not already have installed and would like to allowed your users to select these from your login page and/or users options page then you will need to follow the instructions below . When you upgrade using a distribution, it would have copied over all the images and templates of all the new templates but not added the webmail.ini settings required to have these selectable by the user. The below are the webmail.ini settings that you would add if you upgraded to v3.1i (or higher) and did not already have set up the 2 new templates 'Surge' and 'Smooth'. The example is for a windows system which is using SurgeMail as your web server. If you are using another O/S or web server you will need to change the directories to match your setup.
|
Removing Templates |
If, after you Upgrade or Install WebMail and there are template sets that you do not want your customers to be able to use, all you need to do is edit your 'webmail.ini' file. Locate the 'tpl_set' which matches the template that you do not want to allow and place a '#' character at the being. This will comment out the template and not allow the users to select it from the login page or user option page. Users that might already be using the removed template will automatically default back to the default template. |