test

Sun Java System Messaging Server 6.3 Administration Guide

1.8 Handling sendmail Clients

If end users send messages through sendmail clients, you can configure Messaging Server to work with those clients over protocol. Users can continue to use the UNIX sendmail client.

To create compatibility between sendmail clients and Messaging Server, you can create and modify a sendmail configuration file.

Note –

Each time a new sendmail patch is applied to your system, you will need to modify the submit.cf file as described in the following instructions in To Create the sendmail Configuration File on Solaris 9 Platforms. On Solaris 8, follow the instructions in To Obtain the Proper Version of the /usr/lib/sendmail on Solaris 8.

When you installed previous versions of Messaging Server, the /usr/lib/sendmail binary was replaced with a component of the Messaging Server product. In Messaging Server 6.0 to the current version, this replacement during install is no longer necessary. Therefore, you may need to obtain the proper version of the /usr/lib/sendmail binary from the most current sendmail patch.

On Solaris OS 9 platforms, sendmail is no longer a setuid program. Instead, it is a setgid program.

ProcedureTo Obtain the Proper Version of the /usr/lib/sendmail on Solaris 8

  1. Find the file main-v7sun.mc file in directory /usr/lib/mail/cf and create a copy of this file.

    In the example in this section, a copy called sunone-msg.mc is created.

  2. In the sunone-msg.mc file, add the following lines before the MAILER macros:


    FEATURE(`nullclient’, `smtp:rhino.west.sesta.com’)dnl
MASQUERADE_AS(`west.sesta.com’)dnl
define(`confDOMAIN_NAME’, `west.sesta.com’)dnl

    rhino.west.sesta.com is the localhost name and west.sesta.com is the default email domain as described in 1.3 Creating the Initial Messaging Server Runtime Configuration. In an HA environment, use the logical host name. See Chapter 3, Configuring High Availability for more information about logical hostnames for High Availability.

  3. Compile the sunone-msg.mc file:


    /usr/ccs/bin/make sunone-msg.cf

    The sunone-msg.mc will output sunone-msg.cf.

  4. Make a backup copy of the existing sendmail.cf file located in the /etc/mail directory.

    1. Copy and rename /usr/lib/mail/cf/sunone-msg.cf to sendmail.cf file.

    2. Move the new sendmail.cf file to the /etc/mail directory.

ProcedureTo Create the sendmail Configuration File on Solaris 9 Platforms

  1. Find the file submit.mc file in directory /usr/lib/mail/cf and create a copy of this file.

    In the example in this section, a copy called sunone-submit.mc is created.

  2. Change the following line in the file sunone-submit.mc: 


    FEATURE(”msp’)dn

    to


    FEATURE(”msp’, ”rhino.west.sesta.com’)dnl

    where rhino.west.sesta.com is the localhost name.

    rhino.west.sesta.com is the localhost name and west.sesta.com is the default email domain as described in 1.3 Creating the Initial Messaging Server Runtime Configuration. In an HA environment, use the logical host name. See Chapter 3, Configuring High Availability for more information about logical hostnames for High Availability.

  3. Compile the sunone-submit.mc file:


    /usr/ccs/bin/make sunone-submit.cf

    The sunone-submit.mc will output sunone-submit.cf.

  4. Make a backup copy of the existing submit.cf file in the /etc/mail directory.

    1. Copy and rename /usr/lib/mail/cf/sunone-submit.cf file to submit.cf file.

    2. Move the new submit.cf file to the /etc/mail directory.