Solaris upgrade

These instructions are written on the assumption that the mailwasher fires have been installed in the default locations.

Step	Action
1	Shut down sendmail, and the two MailWasher processes, mpd and mwi.
2	Change to the /var/mwserver directory.
3	Using tar, make a backup of the contents of this directory, eg tar cfz ~/mailwasherdb.tar.gz .
4	Change to the /opt/mwserver directory.
5	Using tar, make a backup of the contents of this directory, eg tar cfz ~/mailwasherexes.tar.gz .
6	Run the mailwasher-x.y.z.bin to install the new version of mailwasher.
7	estart the mpd, mwi and sendmail as above.

If you have any problems, shutdown the mpd, mwi and sendmail, and restore from the backups that you made. The data directory is untouched on upgrade, but the data files may be upgraded to a later version of (Oracle) Berkeley DB. The backup is made to ensure backward compatibility, as well as the usual feelgood factor.

To install the qmail conduit, run the install-qmail-conduit.sh script in the other subdirectory of the MailWasher Server product directory you selected during installation (usually /usr/local/mwserver).

If you would prefer to install the qmail conduit manually, complete the following steps:

Step

Action

Shut down qmail, and the two MailWasher processes, mpd and mwi.

Change to the /var/mwserver directory.

Using tar, make a backup of the contents of this directory, eg tar cfz ~/mailwasherdb.tar.gz .

Change to the /opt/mwserver directory

Using tar,make a backup of the contents of this directory, eg tar cfz ~/mailwasherexes.tar.gz .

Run the mailwasher-x.y.z.bin to install the new version of mailwasher.

Restart the mpd, mwi and qmail as above.

Some user-run qmail sites on the web suggest running the qmail daemons under a resource limit (rlimit), such as set by the softlimit utility or the ulimit shell builtin. This resource limit may need to be increased when you install the qmail conduit (whether you install it using automated or manual installation) as it may not allow enough memory space for the system libraries required by the conduit to be mapped in.

If you see errors such as "error while loading shared libraries: [library name]: failed to map segment from shared object: Cannot allocate memory" or "ld.so.1: bin/qmail-queue: fatal: [library name]: mmap failed: Not enough space" appearing in your mail logs, check your qmail-smtpd configuration (usually in /service/qmail-smtpd/run) for softlimit or ulimit commands and increase the limits, then restart the service using svc (or the appropriate control script, if using a packaged version of qmail); note that just killing the daemon and allowing tcpserver to respawn it is not sufficient as that will not re-run the script with the higher limit.