Caldera Volution Messaging Server Release 1.1.1 Maintenance Pack 4

Late News

Caldera Systems, Inc.

NOTE: Linux information in this document provided for historical purposes only. Go here for more info.

Legal Notice
Revision History
Revision 1.1.120 July 2002

First posting

Revision 1.1.1 MP42 October 2002

Note

Unless otherwise noted in this document or the Getting Started Guide, all known limitations from previous releases and maintenance packs have been resolved in Release 1.1.1.


Table of Contents

Introduction
Compatible Commercial Software
Anti-Virus Solutions
Backup Solutions
Calendar Solutions
Fax Solutions
Known Limitations and Workarounds
Installation
Open UNIX 8 Supplement
Removal
Server Configuration and Administration
POP-Before-SMTP
Increasing the Default Message and Attachment Size
Enabling Local System Users to Receive Mail with the Messaging Server
Client Configuration and Administration
Problems Deleting User Owned Aliases
Documentation Notes
DocView might not be running after VMS is installed.
Dynamic Relay Authentication (DRAC)
Postfix Documentation
Licensing the Messaging Server
Viewing Documentation in Server Manager Help Screens
Creating Messaging Server Accounts on Caldera OpenLinux or Open UNIX 8 Systems

Introduction

Late News provides critical information you need to know before and just after installing the Caldera Messaging Server Maintenance Pack 4 (here after “Messaging Server”).

This document assumes you have already read the Messaging Server Cover Letter, which is included with your distribution media. You should also familiarize yourself with Late News before:

  • reviewing the Messaging Server Getting Started Guide, which is available in a printed book with your Message Server distribution, using the DocView online documentation system when the Messaging Server is installed, and in HTML and PDF format in the /doc/getstart directory on distribution media or ISO image.

  • installing and configuring Message Server.

This document provides information on:

Compatible Commercial Software

Anti-Virus Solutions

  • CA eTrust (http://www.cai.com/)

  • Sophos Anti-Virus (http://www.sophos.com/)

  • Sophos MailMonitor (http://www.sophos.com/)

Backup Solutions

  • Arkeia Backup Solution (http://www.arkeia.com/)

  • BakBone NetVault (http://www.bakbone.com/)

  • Lone Star Software Lone-Tar (http://www.cactus.com/)

  • Microlite BackupEDGE SS (http://www.microlite.com/)

Calendar Solutions

  • Steltor CorporateTime Server (http://www.steltor.com/)

Fax Solutions

  • Faximum Messaging Server (http://www.faximum.com/)

  • VSI-FAX (http://www.vsi.com/)

Known Limitations and Workarounds

Installation

You can now use the Messaging Server graphical user interface to upgrade from previous versions.

The Messaging Server can be installed and licensed on both Caldera OpenLinux Server 3.1.1 and Open UNIX 8 Release 8.0 with Linux Kernel Personality.

Open UNIX 8 Supplement

The Getting Started Guide erroneously recommends that you install the ou800pk2 (Open UNIX 8 Release 8.0.0 Maintenance Pack 2) supplement and ptf8003 (Connectionless connect fix on Linux AF_UNIX sockets) patch before installing the Messaging Server on your Open UNIX 8 system. They have been superseded by Open UNIX 8 Release 8.0.0 Maintenance Pack 4 (ou800pk), which includes new updates as well as fixes from previous supplements. You must install the Maintenance Pack after installing LKP to ensure that the LKP fixes are installed. It is not necessary to remove previous supplements before installing Maintenance Pack 4.

It is available from the:

  • Caldera web site (http;//www.sco.com?support/ftplists/ou8list.html

  • Caldera ftp site

    Enter ftp -p ftp.sco.com and change directories (cd) to pub/openunix8.

    Note

    You must invoke ftp in passive mode (that is, with the -p command option.

Before installation, familiarize yourself with the supplement cover letter. If you have already installed the Messaging Server on your Open UNIX 8 system, the supplement and patch can be safely installed after the Messaging Server has been installed and configured.

Removal

At this time, there are no known removal problems.

Server Configuration and Administration

POP-Before-SMTP

Beginning with release 1.1.1, Volution Messaging Server supports POP-Before-SMTP out of the box via the Dynamic Relay Authentication Control (DRAC) server. This feature prevents people from using the site as a relay unless they previously have authenticated with the server via POP or IMAP.

Increasing the Default Message and Attachment Size

The following includes information on increasing the default message and attachment size in Postfix and in IMP.

Postfix

Use the following information as a supplement to the information found in the Administrator’s Guide Chapter 6, Managing Messaging Server Components, in the section titled, Managing Large Messages and Attachments.

The default message and attachment size in Postfix is 10,240,000B. Use the following information to change the default setting in the Postfix main.cf file:

  1. Open /etc/postfix/main.cf in your favorite editor.

  2. Uncomment the message_size_limit parameter line by removing the hash mark at the beginning of the line.

    The message_size_limit parameter limits the size (expressed in bytes) of a message, including envelope information.

  3. Increase the value (in bytes) on message_size_limit=10240000.

  4. Add the following line:

    mailbox_size_limit=

  5. Enter a value on the mailbox_size_limit= parameter to a value greater than or equal to the message_size_limit parameter.

  6. Reload Postfix using the Server Manager Mail Services menu or by using the following command:

    /etc/rc.d/init.d/postfix/reload

IMP

Use the following information as a supplement to the information found in the Technical Article titled “I get an Undefined Variable warning when trying to attach a large attachment within Volution Messaging Server Webmail” (Ref#116659) available from the Caldera Support Knowledge Base site:

http://www.support.sco.com/caldera/

The default message and attachment size in IMP is 2MB. Use the following information to change the default setting in the php.ini file:

  1. Open /etc/httpd/php.ini in your favorite editor.

  2. Increase the value on upload_max_filesize.

  3. Restart the Apache web server using the following command:

    /etc/rc.d/init.d/httpd restart

If you are running the Messaging Server on Open UNIX 8, you must enter the Linux namespace with the linux command before making these changes.

Note

Check with your network administrator before doing this because very large attachments can cause problems with the mail transport system and network.

Enabling Local System Users to Receive Mail with the Messaging Server

By default, if a user has a Caldera OpenLinux or Open UNIX 8 system account with the User ID as their messaging server account, their mail will be delivered to /var/mail/username rather than to a Messaging Server mailbox. However, you can modify your Postfix configuration to enable them to receive mail from the Messaging Server. Complete the following as root:

  1. Edit the file etc/postfix/main.cf, making the following changes:

    • Comment out the fallback_transport parameter to read:

      #fallback_transport = cyrus

    • Un-comment the mailbox_transport parameter to read:

      mailbox_transport = cyrus

    • Modify the alias_maps parameter to read:

      alias_maps = ldap:ldapsource, hash:/etc/postfix/aliases

  2. Edit /etc/postfix/aliases and add the line:

    root: admin

  3. Initialize the alias database by running the command:

    newaliases

  4. Restart the postfix daemon with the commands:

    postfix stop

    postfix start

When this procedure is complete, mail will only be delivered to Messaging Server users, not system users. In addition, all administrative system email will go to the Messaging Server admin account.

Client Configuration and Administration

Only free/busy calendaring is supported in this release for Outlook clients.

Problems Deleting User Owned Aliases

There are two error messages that might appear when you delete aliases that you own. The error messages, an explanation of circumstances that trigger them, and workaround follow.

ERROR:NET::LDAP::Modify=HASH(0x84818bc)->code:modify
(LDPA_INSUFFICIENT_ACCESS) The client does not have sufficient access to
perform the requested operation

ERROR:10:Unable to recursively remove alias <alias name> from alias
<alias name>
.
.
.
CommandExit Value : 1

While your alias was successfully removed, this message indicates that your alias is a member of an alias owned by another user and that your alias was not removed from the other users alias due to an erroneous security violation. This might present a problem when the owner of the alias of which your alias is a member attempts to delete his/her alias.

Member address problems:
The following entries are not recognizable email addresses:
aliasname@hostname.com

This error message indicates that the alias being removed was not deleted because it has as a member, an alias that no longer exists. In this example the error mesage indicates that the alias, aliasname@hostname.com does not exist.

Use the following workaround to remove your alias and resolve the error:

  1. Create the non-existent alias indicated in the error message. In this example the alias is aliasname@hostname.com.

    Do not add any members to this alias.

  2. Delete your alias.

  3. Delete the alias aliasname@hostname.com.

  4. Repeat this procedure for additional aliases that must be deleted so that your alias can be properly removed.

Documentation Notes

DocView might not be running after VMS is installed.

In situations where OpenLinux is newly installed followed by an installation of the Messaging Server, DocView, the documentation viewing system, might not be running. Start DocView from the Messaging Server web console or by running the following command:

/etc/rc.d/init.d/docview restart

If at this time the Apache web server stops, restart it using the following command:

/etc/rc.d/init.d/httpd restart

Dynamic Relay Authentication (DRAC)

For information on DRAC, refer to the following man pages:

rpc.drac-Describes the DRAC daemon.

dracauth-Describes the DRAC programming interface.

Postfix Documentation

For information on Postfix refer to DocView under the heading Component Documentation. There is a link to Wietse’s Postfix Project page. Third-party books such as, Postfix by Richard Blum (published by Sams Publishing) are also helpful.

Licensing the Messaging Server

“Licensing” in the Getting Started Guide describes some of mail server configurations available for the Messaging Server although others might also be available in your area. Contact your Caldera representative to design a mail service solution that fits your needs.

Viewing Documentation in Server Manager Help Screens

The Server Manager includes Help screens that connect to individual topics in the Administrator’s Guide. In addition to describing the Server Manager, the Administrator’s Guide also includes detailed information about advanced administrative procedures and Messaging Server components. We recommend using the DocView documentation server for viewing this information; some of the Administrator’s Guide hotlinks cannot be displayed in the Server Manager Help screens. For more information about DocView, see “Viewing OpenLinux Documentation” in the Getting Started Guide.

Creating Messaging Server Accounts on Caldera OpenLinux or Open UNIX 8 Systems

The Getting Started Guide erroneously states that you will receive an error when you try to create a Messaging Server account on a Caldera OpenLinux or Open UNIX 8 system that already has a local user account with the same User ID. You can successfully create such an account, but their mail will be delivered to /var/mail/username rather than to a Messaging Server mailbox. To enable delivery to a Messaging Server mailbox, follow the procedure described in “Enabling Local System Users to Receive Mail with the Messaging Server”.