| |
MailSite Knowledge Base
MailSite Express on a separate server
Document #:10103
Applies To:
- MailSite
6.x
- MailSite
7.x
- MailSite
8.x
- MailSite
9.x
Synopsis: This document details how to deploy MailSite Express on a different server to that running the core MailSite services.
NOTE: Always ensure you are running the latest release of MailSite and apply any available hotfixes.
More Information:
For these installation instructions, we will call the server which MailSite Express is installed: HOST1 and the server which the MailSite engine is installed: HOST2
MAILSITE ENGINE SET UP
on HOST2 set up a share for the mailbox root directory:
For example: \\host2\box
In the MailSite console of HOST2, set the default mailbox root directory to the share (also known as UNC path), NOT to a local path:
For example: \\host2\box
The MailSite services need to run as MailSite-user or another user you have specified with service privileges. You cannot run the services as system because the mailbox directory is no longer LOCAL to MailSite Express.
MAILSITE EXPRESS SET UP
On HOST1, when running the MailSite installer, you should select to install ALL options. After the installation is complete you can go into the Control Panel | Administrative Tools | Services and disable the MailSite services.
Set the SMTP and IMAP servers to the IP address of HOST2. This is done within the expresscfg.asp file located in the mailsite\express\web\ directory.
Next you need to set the user Express is running under to the MailSite-user, or the user you specified on HOST2, to the same login name and password. You will need to do this in IIS under the virtual directory of EXPRESS, to set the permission, follow the steps below:
- Open IIS
- Right click on the EXPRESS virtual directory
- Select properties
- click on DIRECTORY SECURITY
- Click on EDIT
- Add the USER you defined on HOST2
- If using a Domain user account enter the password and do not check the box which says: "allow IIS to control password". This will only work for local NT accounts
QUICK EXPLANATION
Express (HOST1) will look for the user's mailbox directory by asking MAILMA on the IMAP server (host2) for location, thus:
MAILMA says \\host2\box\username
Express then opens that folder for the message files.
POINTS OF FAILURE
- Mailbox root dir for a domain is local path instead of UNC
- Services were installed as SYSTEM
- MailSite user account not created on web server
- MailSite user created on web server, but different password
- The Mailbox directory was has not been shared
- The UNC path was not assigned to the mailbox root directory. Example: \\HOST\Share_Name (or the wrong location)
- Items 6 & 7 within the Expresscfg.asp file have not been set to the correct IP address of the MailSite server (Default "localhost")
- MAILMA not running (not all sites run this)
- IMAP server in expresscfg.asp specified by Windows hostname, not fully-qualified host.domain name (full name forces TCP/IP through MAILMA)
- The IIS Anonymous account under Directory Security was not set with the correct account which has access to the needed Directories
- If a domain account is used for MailSite-user, Active Directory may have group policies which may prevent access to everything (not just express) make sure the account used is not restricted by group policies
Last revised 2009-9-14
|
|