Sentrion Overview Sentrion Platform Sentrion Mimecast Hard Appliances Virtual Appliances
Overview Policy Compliance Secure Content Filtering Cloud Partner Enterprise Community
Overview Download Security Support News Documentation Tips & Tricks DKIM FAQ Misc Milters
Overview Directory Synchronization Messaging Architecture Review High Volume Mail HIPAA Policy QUICKStart Implementation Performance Tuning Training Services Overview Message Routing and
Configuration
Message Policy
Management
Connection Control /
Attack Prevention
Directory Configuration
and Management
Overview Milter Community Industry Organizations System Integrators & Distributors
Overview Silver Support Gold Support Platinum Support Security Advisories Contact Support
Overview Customers Press Room Board of Directors Leadership
Management Team
Join Our Team Contact Us
Overview Ask the Experts Security Chalk Talks Collateral Product Reviews & Awards IP Reputation Check Real-time Outbreak Monitor
Sendmail Inc.

HOME | CUSTOMER LOGIN
Sentrion Message Processors
Sentrion Application Store
Services
Partners
Support
Company
Resources
Open Source
 
    Open Source
  • Overview
  • Download
  • Security
  • Support
  • News
  • Documentation
  • Tips and Tricks
  • DKIM
  • FAQ
  • Misc
  • Milters
  • Current Release Notes
  • Older Release Notes
  • Installation and Operation Guide
  • Configuration Readme
  • Books
  • Useful Links
  • Email Explained
  • M4 Information
  • Vendor Information
This document is intended as a guide for users and administrators who are concerned about the sendmail-related issues they may encounter when migrating from older releases of Solaris to Solaris 9.
Section 4 of the page titled Differences between Sun and Berkeley versions of sendmail explains in detail the semantics and syntax for V1/Sun sendmail configuration files. As of Solaris 9, these are no longer supported. This means that the syntax will not be accepted, which may cause sendmail to exit with an error if run with a V1/Sun configuration file, and the semantic changes will disappear; i.e., the behavior will revert to that of Berkeley sendmail.

There are two other sets of features which are no longer supported in Solaris 9's version of sendmail: remote mode, and the Sun reverse alias features.

Remote Mode
The remote mode feature was used to route and address mail via a mail server from which /var/mail was remotely mounted via NFS. This was non-standard, however: there is no logical relationship between where /var/mail is mounted from and either where mail should be routed to or how mail should be addressed. This feature is no longer supported as of Solaris 9. For routing, the SMART_HOST feature, documented on our Masquerading and Relaying page, which is already enabled in the Solaris subsidiary configuration file, takes care of this by default.

Regarding addressing: remote mode, when in use, set the sender's address to that of the remote mail server. With the removal of remote mode, the default subsidiary configuration file will, as of Solaris 9, use the client host's name just like the main configuration file does. Users who would prefer to use a different host name may wish to study our Masquerading and Relaying page. Here is a primer on how to change the default configuration to use masquerading:

  1. cd /usr/lib/mail/cf
  2. cp subsidiary.mc myhost.mc
  3. Edit myhost.mc: add the line
    MASQUERADE_AS(`foo')
    
    after the DOMAIN line but before the MAILER lines, where foo is the host name you would like outbound mail messages to have. Note that $m is the macro for the local domain name, which is a common masquerade value. (Note: see our Sun migration page for some gotchas with fully-qualified host names and the domain portion thereof.)
  4. /usr/ccs/bin/make myhost.cf
  5. cp myhost.cf /etc/mail/sendmail.cf
  6. /etc/init.d/sendmail restart

 

Sun Reverse Alias features
There were three Sun-specific features for reverse-aliasing which were never documented:
FEATURE(`sun_reverse_alias_files')
FEATURE(`sun_reverse_alias_nis')
FEATURE(`sun_reverse_alias_nisplus')
These features were proprietary, and are no longer supported as of Solaris 9. The preferred method for reverse-aliasing is the genericstable feature, documented in our Configuration Features page and in our Virtual Hosting page.

Solaris is a trademark of Sun Microsystems, Inc. in the United States and other countries.
Sun Info Home Vendor Info Home


Site Map | Privacy Policy | Terms & Conditions | Copyright © 1998-2016 Sendmail, Inc. All Rights Reserved.