|
|
|
Section 2.
Before Installing the SCOoffice Server |
||
|
|
||
Table of Contents
Planning a SCOoffice Server Configuration
Allocating a Separate Filesystem for the SCOoffice Server Software
Number of Mail and Calendar Clients
Mail Quotas and Mailbox Creation
Junk Mail Filtering and Virus Protection
How the SCOoffice Server Alters Your System
|
OS: |
UnixWare 7.1.4 with MP3 or later OpenServer 6.0.0 with MP2 or later |
|
RAM: |
Minimum 256 MB + 1 MB per user |
|
Disk space: |
Minimum 600 MB + allocation for user |
|
Networking: |
TCP/IP networking with DNS name |
Compatible software products (such as backup solutions) may have additional RAM and disk space requirements.
We recommend installing the SCOoffice Server on a freshly-installed UnixWare or OpenServer system that is dedicated for mail server use.
To ensure system stability, it's recommended that the SCOoffice Server software be installed in a non-root filesystem in order to prevent the root filesystem from becoming filled by the mail store over time. To do this, specify a separate /opt/insight filesystem during the UnixWare or OpenServer installation process.
Estimate the number of mail clients your system must service for a reasonable period of time into the future. This will help you determining licensing and system hardware needs. Based on these decisions, you might also want to set mail quotas for users, or set up multiple servers (see “Distributed Mail” in the Server Administration Guide for details).
The SCOoffice Server allows you to set quota limits on the size of user mail stores, which include their inboxes and folders. Individual quotas can be defined when a user is created. Default quotas can be also be defined by selecting ConfigurationàServicesàCyrus IMAP using the Web administration console. Set the autocreatequota parameter (under “Preferences”) to the maximum size desired.
You have the option of creating user mailboxes automatically or letting the user’s mail client create them. Note that the server will create mailboxes in the language configured for the server; if users need to use a different language setting, let the clients create the mailboxes by de-selecting the Create Mailbox option when creating users.
Global Disclaimers (Mail DeliveryàGlobal Disclaimers) are legal disclaimers that can be automatically appended to email messages. Refer to the Mail Delivery topic in the Server Administration Guide for more information. If disclaimers are not needed, the feature can be disabled to improve system performance (the default is disabled).
The SCOoffice Server provides protection against junk mail (unsolicited email or spam) and viruses. Because filtering can be implemented globally or per user, we recommend that you set junk mail policies before creating mail client users. AMaViS is integrated in SCOoffice Server, along with Clam Anti-Virus and Spamassassin; see the chapters for these topics in the Server Administration Guide for more information. If content filtering is not needed, this feature can be disabled to improve system performance (the default is enabled).
To use the server command line utilities, you must set the library path variable in your environment or from the command line:
If running the Cyrus utilities, you must also su to the cyrus account.
The following services will be disabled in the /etc/inetd.conf file:
· ftp 21
· imap 143
· pop3 110
· smtp 25
The following scripts in the /etc/rc2.d directory will be disabled:
· P86mmdf
· P86sendmail
· P90apache
SCOoffice Server includes its own SMTP, IMAP, POP3, FTP, LDAP, and HTTP servers.
The following users and groups are added to the system: amavis, apache, cyrus, filter, jabber, nobody, postdrop, postfix, proftpd.
Most of the SCOoffice Server software is installed in the /opt/insight directory (documentation is installed in /usr/share). It is not possible to change the location of the server components.
|
Section1. Introducing the SCOoffice
Server |
Section 3. Installation and Removal |