Preface
This guide explains how to administer the Sun JavaTM System Messaging Server and its accompanying software components. Messaging Server provides a powerful and flexible cross-platform solution to meet the email needs of enterprises and messaging hosts of all sizes using open Internet standards.
For revision history of this document, see Sun Java System Messaging Server 6.3 Administration Guide Revision History.
Who Should Use This Book
You should read this book if you are responsible for administering and deploying Messaging Server at your site. You should also have read the Sun Java Communications Suite 5 Deployment Planning Guide.
Before You Read This Book
This book assumes that you are responsible for administering the Messaging Server software and that you have a general understanding of the following:
-
The Internet and the World Wide Web
-
Messaging Server protocols
-
Sun Java System Directory Server and LDAP
-
System administration and networking
-
General deployment architectures
How This Book Is Organized
This manual contains the following chapters and appendix:
Table P–1 How This Book Is Organized|
Chapter |
Description |
|---|---|
|
Preface |
General information about using this book. |
|
Describes the tasks required to get you to a point where you have a functioning Messaging Server. |
|
|
Chapter 2, Upgrading from Messaging Server 5.2 to Sun Java System Messaging Server |
Describes how to upgrade from Messaging Server 5.2 to this version of Messaging Server. |
|
Provides information on how to configure the Veritas Cluster Server and Sun Cluster high availability clustering software for use with the Messaging Server. |
|
|
Describes the general Messaging Server tasks. |
|
|
Describes how to configure your server to support POP, IMAP and HTTP services |
|
|
Explains how to enable Single Sign-On. |
|
|
Chapter 7, Configuring and Administering Multiplexor Services |
Describes the Messaging Multiplexor (MMP) for standard mail protocols (POP, IMAP and SMTP). |
|
Provides a conceptual description of the MTA. |
|
|
Describes Address Translation and Routing. |
|
|
Describes MTA services and configuration. |
|
|
Describes how to configure rewrite rules in the imta.cnf file. |
|
|
Explains how to use channel keyword definitions in the MTA configuration file imta.cnf. |
|
|
Describes how to use pre-defined channel definitions in the MTA. |
|
|
Chapter 14, Integrating Spam and Virus Filtering Programs Into Messaging Server |
Describes how to integrate and configure spam and virus filtering software with Messaging Server. |
|
Chapter 15, Handling Forged Email Using the Sender Policy Framework |
Describes a technology that can detect and reject forged email during the SMTP dialogue. |
|
Describes LMTP operation and deployment. |
|
|
Describes the vacation autoreply mechanism. |
|
|
Discusses how to filter mail based on its source (sender, IP address and so on) or header strings. |
|
|
Describes a repository process that supplants conn_throttle.so, providing similar functionality but extending it across the Messaging Server installation. |
|
|
Describes the message store and its administration interface. |
|
|
Describes archiving concepts for Messaging Server. |
|
|
Chapter 22, Configuring the JMQ Notification Plug-in to Produce Messages for Message Queue |
Describes how to configure a JMQ notification plug-in to produce messages to be consumed by clients in a Message Queue service. |
|
Describes how to configure security and access control to the messaging server. |
|
|
Chapter 24, Administering S/MIME for Communications Express Mail |
Describes how to administer S/MIME. |
|
Describes Messaging Server logging facility. |
|
|
Describes common tools, methods, and procedures for troubleshooting the MTA. |
|
|
Describes the monitoring of the Messaging Server. |
|
|
Describes how to enable SNMP support for the Messaging Server. |
|
|
Appendix B, Administering Event Notification Service in Messaging Server |
Describes how to enable the Event Notification Service Publisher (ENS Publisher) and administer Event Notification Service (ENS) in Messaging Server. |
|
Describes how to implement the Short Message Service (SMS). |
|
|
Provides worksheets by which you can plan your installation. |
Messaging Server Documentation Set
The following table summarizes the books included in the Messaging Server core documentation set.
Table P–2 Messaging Server Documentation|
Document Title |
Contents |
|---|---|
|
Sun Java System Messaging Server 6.3 Administration Reference |
Provides detailed reference information on Messaging Server commands, configutil parameters, configuration files and options, and supported standards. |
|
Contains the information you need to deploy Sun Java System Communications Services including Messaging Server. |
|
|
Sun Java System Delegated Administrator 6.4 Administration Guide |
Explains how to configure and administer Sun Java System Communications Services Delegated Administrator. Also describes the Delegated Administrator commands. |
|
Describes how to migrate Sun Java System LDAP Directory data from LDAP Schema 1 to LDAP Schema 2 for System Messaging Server and Calendar Server. |
|
|
Sun Java Communications Suite 5 Event Notification Service Guide |
Describes the Event Notification Service (ENS) architecture and APIs for Messaging Server and Calendar Server. It gives detailed instructions on the ENS APIs that you can use to customize your server installation. |
|
Contains important information available at the time of release of Sun Java System Messaging Serve. New features and enhancements, known issues and limitations, and other information are also addressed here. |
|
|
Serves as a reference for schema information for Messaging Server and Calendar Server. |
|
|
Sun Java System Communications Express 6.3 Administration Guide |
Describes how to administer Communications Express and its accompanying software components. |
|
Sun Java System Communications Express 6.3 Customization Guide |
Explains how to customize the look and feel of Communications Express. Focuses on how to perform the most commonly requested customizations. |
|
Contains the information you need to install the Sun Java Enterprise System (Java ES) software. |
|
|
Sun Java System Messaging Server 6 2005Q4 MTA Developer’s Reference |
Describes the Messaging Server Message Transfer Agent (MTA) Software Development Kit (SDK) and Callable Send facility. |
|
Glossary. |
|
|
Topical links to Communications Suite Documentation. |
In addition, use the following URL to see the documentation that applies to all Communications Services products:
Related Books
The http://docs.sun.com web site enables you to access Sun technical documentation online. You can browse the archive or search for a specific book title or subject.
For other server documentation related to deploying Messaging Server, go to the following:
-
Access Manager documentation: http://docs.sun.com/app/docs/coll/1292.2
-
Calendar Server documentation: http://docs.sun.com/app/docs/coll/1313.2
-
Communications Express documentation: http://docs.sun.com/app/docs/coll/1312.2
-
Directory Server documentation: http://docs.sun.com/app/docs/coll/1224.3
-
Instant Messaging documentation: http://docs.sun.com/app/docs/coll/1309.2
-
Messaging Server documentation: http://docs.sun.com/app/docs/coll/1312.2
Default Path and File Names
The following table describes the default path and file name that are used in this book.
Table P–3 Default Paths and File Names|
Placeholder |
Description |
Default Value |
|---|---|---|
|
msg-svr-base |
Represents the base installation directory for Messaging Server. The Messaging Server default base installation and product directory depends on your specific platform. |
Solaris systems: /opt/SUNWmsgsr |
Typographic Conventions
The following table describes the typographic changes that are used in this book.
Table P–4 Typographic Conventions|
Typeface |
Meaning |
Example |
|---|---|---|
|
AaBbCc123 |
The names of commands, files, and directories, and onscreen computer output |
Edit your .login file. Use ls -a to list all files. machine_name% you have mail. |
|
AaBbCc123 |
What you type, contrasted with onscreen computer output |
machine_name% su Password: |
|
AaBbCc123 |
A placeholder to be replaced with a real name or value |
The command to remove a file is rm filename. |
|
AaBbCc123 |
Book titles, new terms, and terms to be emphasized (note that some emphasized items appear bold online) |
Read Chapter 6 in the User's Guide. A cache is a copy that is stored locally. Do not save the file. |
Shell Prompts in Command Examples
The following table shows default system prompts and superuser prompts.
Table P–5 Shell Prompts|
Shell |
Prompt |
|---|---|
|
C shell on UNIX and Linux systems |
machine_name% |
|
C shell superuser on UNIX and Linux systems |
machine_name# |
|
Bourne shell and Korn shell on UNIX and Linux systems |
$ |
|
Bourne shell and Korn shell superuser on UNIX and Linux systems |
# |
Symbol Conventions
The following table explains symbols that might be used in this book.
Table P–6 Symbol Conventions|
Symbol |
Description |
Example |
Meaning |
|---|---|---|---|
|
[ ] |
Contains optional arguments and command options. |
ls [-l] |
The -l option is not required. |
|
{ | } |
Contains a set of choices for a required command option. |
-d {y|n} |
The -d option requires that you use either the y argument or the n argument. |
|
${ } |
Indicates a variable reference. |
${com.sun.javaRoot} |
References the value of the com.sun.javaRoot variable. |
|
- |
Joins simultaneous multiple keystrokes. |
Control-A |
Press the Control key while you press the A key. |
|
+ |
Joins consecutive multiple keystrokes. |
Ctrl+A+N |
Press the Control key, release it, and then press the subsequent keys. |
|
-> |
Indicates menu item selection in a graphical user interface. |
File -> New -> Templates |
From the File menu, choose New. From the New submenu, choose Templates. |
Accessing Sun Resources Online
The docs.sun.com web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities.
To access the following Sun resources, go to http://www.sun.com.
-
Downloads of Sun products
-
Services and solutions
-
Support (including patches and updates)
-
Training
-
Research
-
Communities (for example, Sun Developer Network)
Third-Party Web Site References
Third-party URLs are referenced in this document and provide additional, related information.
Note –
Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the full document title and part number. The part number is a 7-digit or 9-digit number that can be found on the book's title page or in the document's URL.
Sun Java System Messaging Server 6.3 Administration Guide Revision History
|
Version |
Date |
Description of Changes |
|---|---|---|
|
14 |
15 February 2008 |
Fixed a number of documentation bugs. Changes are listed below. |
|
13 |
22 July 2007 |
|
|
12 |
8 June 2007 |
|
|
11 |
14 April 2007 |
|
|
10 |
March 2007 |
Initial release of this technical note. |
Administration Guide Revision Changes from Version 14 to 15
These are Administration Guide changes from 819-4428-14 to 819-4428-15. < > angle bracketed words indicate deleted text with replaced by words immediately following. [ ] bracketed words indicated new text.
Chapter 1, Post-install Tasks and Layout
In this section, added the following note regarding Solaris 10 at the end of the discussion of adding the FQDN in the etc/hosts/ and related files:
Note –
On Solaris OS 10 U3 and earlier platforms, you not only have to add the Fully Qualified Domain Name (FQDN) to the /etc/hosts file, but also to the/etc/inet/ipnodes file. Otherwise, you will get an error indicating that your host name is not a Fully Qualified Domain Name. From Solaris OS 10U4 onwards, the contents of the /etc/inet/ipnodes and /etc/hosts files have been merged together into just the/etc/hosts file. Applying kernel patch 120011-14 on any Solaris 10 system will also perform the merge, and subsequent removal of the/etc/inet/ipnodes file.
New level 2 section: 1.10.1 Java Message Queue (JMQ) Tuning.
Chapter 11, Configuring Rewrite Rules
Added the following paragraph to 11.4.2. Repeated Rewrites Template, A%B: [Note, however, that while the special A%B form does cause rewriting of the current domain to restart, it is actually just a continuation of the current rewriting process. It does not rewrite the entire process from the beginning. It does not perform the $* pattern when it goes through the second time.]
Chapter 12, Configuring Channel Definitions
Removed immnourgent
12.4.1 Configuring SMTP Channel Options
Added the following paragraph: <SMTP channel options that pertain to a destination channel should be placed in the appropriate channel option file (that is, tcp_local_option, tcp_auth_option, tcp_intranet_option). SMTP channel option files that pertain to a source channel MUST be placed in the tcp_local_option file since all messages come into the MTA via the tcp_local channel before any channel switching takes place for incoming messages.>
Chapter 14, Integrating Spam and Virus Filtering Programs Into Messaging Server
Removed references to the SOCKS_USERNAME and SOCKS_PASSWORD options from the book. The references appeared in the following sections in Chapter 14:
Removed all references and instructions regarding the LMTP native channel.
Chapter 18, Mail Filtering and Access Control
Processing Control ($C, $L, $R, $E)
Rewrote this section.
Changed description of $T text to the following: If bit 1 (value 2) of the LOG_CONNECTION MTA option is set and the $N flag is set so that the connection is rejected, then $T outputs the entire right hand side text in a "T" record. The T log entry will include the entire mapping result string ($N and its string). In contrast, bit 4 of LOG_CONNECTION is a different effect: it will cause material after two vertical bars to be included in normal "C" (connection close) records.
18.3.4 PORT_ACCESS Mapping Table
Added a new table. Fixed other table.
18.3.5 IP_ACCESS Mapping Table
<source-channel|address-count|address-current|ip-current|hostname>source-channel|address-current|address-count|ip-current|hostname
18.4 When Access Controls Are Applied
Added new information at the bottom of this section about when access control mapping tables are applied.
18.7.4 To Use DNS Lookups Including RBL Checking for SMTP Relay Blocking
Fixed some errors in the code and added new text added regarding the PORT_ACCESS table being probed both by the dispatcher, when accepting connections, and by the tcp_smtp_server process under certain circumstances.
Chapter 19, Throttling Incoming Connections Using MeterMaid
New note added to the bottom of 19.3 Configutil Parameters for MeterMaid
Chapter 20, Managing the Message Store
Globally replaced moveuser with MoveUser. Note capitalization.
To Add an Email Group to a Shared Folder
readership -s user/gregk/<tennis>gardening tennis@sesta.com lrp
<Age of message in days before being expunged. (integer)>Number of days in the message store before being expunged. (integer)
20.14.4.9 IMAP Events Become Slow
Brand new section.
Added new material to the Note: This is still true, but expire rules using header constraints (example: expiring a message with a specific subject line) are not supported. <Also, regular expressions in the expire rules created with configutil need to be POSIX compliant rules. If you want to use UNIX compliant regular expressions you will have to use the store.expire file. In addition, using both configutil options and the global store.expirerule configuration file is not supported. If the configuration file is present, configutil options are not used.> In any case, it is best to use store.expirerule to specify all expiration rules.
20.11.4 To Monitor Quota Limits
Removed imquotacheck -i. No longer valid.
20.10.2 To Move Mailboxes to a Different Disk Partition
<Make sure user is disconnected from their mailbox during the migration process . . .> The user does not have to be disconnected from their mailbox during this migration process.
20.12.8 Troubleshooting Backup and Restore Problems and To Migrate User Mailboxes from One Messaging Server to Another While Online
Added the following text: When imsrestore or any processing intensive operation takes significantly more system resources than normal, and continues doing so longer than the msprobe interval, there may be a temporary backlog of DB transaction log files to be cleared. If there are more files than specified in local.store.maxlog, then msprobe may erroneously restart all the processes during a restore. To prevent this from happening, disable msprobe during the imsrestore.
20.14.4.1 Reduced Message Store Performance
Added this section, which basically cross-references Tuning the mboxlist Database Cache
To Move Mailboxes Using an IMAP client
In step 2, changed <local.store.relinker to enable> to [Set local.store.relinker.enabled] to yes]
To Move Mailboxes Using the MoveUser Command
In step 2, changed <local.store.relinker to enable> to [Set local.store.relinker.enabled] to yes]
To Move Mailboxes Using the imsimport Command
In step 2, changed <local.store.relinker to enable> to [Set local.store.relinker.enabled] to yes]
Chapter 23, Configuring Security and Access Control
23.7 Configuring Client Access to POP, IMAP, and HTTP Services
Discussed the LDAP method of configuring client access. Added cross-references to the LDAP attributes mailAllowedServiceAccess in Sun Java Communications Suite 5 Schema Reference and mailDomainAllowedServiceAccess in Sun Java Communications Suite 5 Schema Reference
Chapter 24, Administering S/MIME for Communications Express Mail
Rewrote this section.
Administration Guide Revision Changes from Version 12 to 14
These are Administration Guide changes from 819-4428-12 to 819-4428-14. < > angle bracketed words indicate deleted text with replaced by words immediately following. [ ] bracketed words indicated new text. Note that only one change was between 12 and 13, and that was the addition of this Revision Guide History.
Chapter 3, Configuring High Availability
4.5.1 Automatic Restart in High Availability Deployments
Chapter 4, Configuring General Messaging Capabilities
Table 4–5, entry for local.autorestart.timeout <fails more than twice> fails more than once
Added this new section which talks about disabling XADR, XCIR, XGEN, and XSTA.
Chapter 9, MTA Address Translation and Routing
9.1.3.8 Delivery Options Processing
In the example: <=$M%$\\> [=$M%$\]
Chapter 10, About MTA Services and Configuration
Added new information about setting MAX_MESSAGES.
Chapter 12, Configuring Channel Definitions
smtp (This keyword is equivalent to <smtp_crorlf> smtp_crlf.)
12.4.2.1 Channel Protocol Selection and Line Terminators
<The keyword smtp_crlf means that lines must be terminated with a carriage return (CR) line feed (LF) sequence. The keyword smtp_lf or smtp means that an LF without a preceding CR is accepted. Finally, smtp_cr means that a CR is accepted without a following LF. These option affect only the handling of incoming material.>
[The keyword smtp_crlf or smtp means that lines must be terminated with a carriage return (CR) line feed (LF) sequence. The keyword smtp_lf means that an LF without a preceding CR is accepted as well as the standard CRLF sequence. The keyword smtp_cr means that a CR is accepted without a following LF. Finally, smtp_crorlf means that any of CR, LF, or the standard CRLF sequence are allowed as the SMTP line terminator. These option affect only the handling of incoming material.]
12.6.14 Handling Personal Names in Address Header Lines
Added: If the PERSONAL_NAMES mapping table returns 8-bit characters, they are UTF-8 encoded.
Chapter 13, Using Predefined Channels
Rewrote a number of small sections to make clearer. This in response to bug 4902284.
Chapter 14, Integrating Spam and Virus Filtering Programs Into Messaging Server
14.2.3 Specifying Actions to Perform on Spam Messages
Table 14–1, MTA Spam Filter Options. Rewrote spamfilterX_final
14.9 Cloudmark Anti-Abuse Client
Mentioned support for Cloudmark anti-spam solution.
14.7 Support for Sieve Extensions
Added that spamadjust and spamtest can be also be used with Brightmail.
16.5.1 To Configure Back End Stores with LMTP and a Minimal MTA
tcp_lmtpss lmtp [flagtransfer]
Chapter 18, Mail Filtering and Access Control
18.3 Access Control Mapping Table Flags
Table 18–2 — Enhanced description of $X.
Chapter 20, Managing the Message Store
Wherever hashdir was recommended as the command to use for finding the directory containing a specified folder, mboxutil -lxp pattern was recommended instead.
20.2.1 Valid UIDs and Folder Names
Rewrote this section and renamed it to Valid UIDs and Folder Names.
Chapter 26, Troubleshooting the MTA
26.2.7 Starting and Stopping Individual Channels
Added the following:
NOTE - The command imsimta qm start/stop channel may fail if run simultaneously for many channels at the same time. The tool might have trouble updating the hold_list and could report: QM-E-NOTSTOPPED, unable to stop the channel; cannot update the hold list." imsimta qm start/stop channel should only be used sequentially with a few seconds interval between each run.
If you only want the channel to run between certain hours, use the following options in the channel definition section in the job controller configuration file:
urgent_delivery=08:00-20:00 normal_delivery=08:00-20:00 nonurgent_delivery=08:00-20:00
Appendix C, Short Message Service (SMS)
< These entries establish mappings to be applied to . . .> Text removed. Body mappings are not supported.
Administration Guide Revision Changes from Version 10 to 12
These are Administration Guide changes from 819-4428-10 to 819-4428-12. < > angle bracketed words indicate deleted text with replaced by words immediately following. [ ] bracketed words indicated new text.
Chapter 1, Post-install Tasks and Layout
1) <$(192.45.67.89/24)> $(192.45.67.89/32)
2) <first 24> full 32
When you <upgraded>installed previous versions of Messaging Server, the /usr/lib/sendmail binary was replaced with a component of the <sendmail>Messaging Server product. In Messaging Server, Messaging Server {6.0 to the current version,} this replacement during <upgrade>install is no longer <occurs>necessary. Therefore, you may need to obtain the proper version of the /usr/lib/sendmail binary from the most current sendmail patch.
<FEATURE("nullclient', "smtp:rhino.west.sesta.com')dnl
MASQUERADE_AS("west.sesta.com')dnl
define("confDOMAIN_NAME', "west.sesta.com')dnl>
Replaced by:
FEATURE(`nullclient', `smtp:rhino.west.sesta.com')dnl
MASQUERADE_AS(`west.sesta.com')dnl
define(`confDOMAIN_NAME', `west.sesta.com')dnl
Chapter 2, Upgrading from Messaging Server 5.2 to Sun Java System Messaging Server
All of this moved to the technical article entitled: Upgrading from Messaging Server 5.2 to Sun Java System Messaging Server.
Chapter 3, Configuring High Availability
3.1 Supported Versions Moved to Release Notes
3.4.1 Sun Cluster Requirements. Version requirements are moved to Release Notes.
Chapter 4, Configuring General Messaging Capabilities
4.4.1 To Start and Stop Services in an HA Environment
To Start, Stop, Restart in Veritas <1.3, 2.0, 2.1,>3.5, 4.0, 4.1 and <3.5> 5.0 Environments
4.4.2 To Start and Stop Services in a non-HA Environment. Minor typos.
4.4.3 Starting and Stopping a Messaging Server Running in MTA-only Mode. New section!
4.6 To Schedule Automatic Tasks
1) <A fully qualified command pathname is required.>Paths can be relative to msg-svr-base or absolute paths. See Pre-defined Automatic Tasks for relative path examples.
2) <send SIGHUP to> refresh the scheduler process: <kill -HUP> refresh sched [scheduler_pid]
<20,40,60> 0,20,40
4.8 To Set a User-Preferred Language
<accept-language> Accept-Language (twice!)
Chapter 5, Configuring POP, IMAP, and HTTP Services
5.2.1 To Allow Log In without Using the Domain Name
<inetdomainsearchfilter> inetDomainSearchFilter
<You don't need to disable password login to enable certificate-based login. If password login is enabled, and if> If
<Ibiff> iBiff (twice)
<As mailsrv run> Run:
<local.store.notifyplugin.ensHos> local.store.notifyplugin.enshost <local.store.notifyplugin.ensHost> local.store.notifyplugin.enshost <local.store.notifyplugin.ensEventKey> local.store.notifyplugin.enseventkey <local.store.notifyplugin.ensEventKeyl> local.store.notifyplugin.enseventkey
Chapter 6, Enabling Single Sign-On (SSO)
No changes.
Chapter 7, Configuring and Administering Multiplexor Services
7.2.3 Certificate-Based Client Authentication
<certmap>certmap.conf
To Configure MMP with SSL (Version 13)
Steps 2, 3, Note removed:
<2. If you have installed the Admin Server . . . >
<3. Since the sslpassword.conf file is set . . . >
< NOTE: An alternative approach to steps 1-8 . . .>
Steps 5 & 6 consolidated into a single step: [If you do not want to use SSL between the . . .]
7.4.1.1 IMAP Configuration Example
1) </opt/SUNWmsgsr/config/cert7.db> /opt/SUNWmsgsr/config/cert8.db
2) <"".> /opt/SUNWmsgsr/config/sslpassword.conf
7.4.1.2 POP Configuration Example
<It also provides a spoof message file.>
7.5.1 To Configure Mail Access with MMP
<is not configured automatically, it has to be explicitly configured. In addition, the MMP>
7.5.2 To Set a Failover MMP LDAP Server
1) <IMAPProxyAservice.cfg>ImapProxyAservice.cfg
2) </o=INTERNET"> /o=internet
3) [Make sure there is a space between the host names in the above configuration.]
No substantive changes.
Chapter 9, MTA Address Translation and Routing
9.1.1.2 Domain Map Determination of Domain Locality
Appended to end of section:
[Two MTA options support more efficient domain lookups from user base domain names. They are LDAP_BASEDN_FILTER_SCHEMA1, which is a string specifying a filter used to identify Schema 1 domains when performing user base domain name searches. The default is the value of LDAP_DOMAIN_FILTER_SCHEMA1 if that MTA option is specified. If neither option is specified the default is (objectclass=inetDomain). LDAP_BASEDN_FILTER_SCHEMA2 is a string specifying additional filter elements used to identify Schema 2 domains when performing user base domain name searches. The default is the value of LDAP_DOMAIN_FILTER_SCHEMA2, if that MTA option is specified. If neither option is specified, the default is an empty string.]
Added to bulleted MTA option list: LDAP_DOMAIN_ATTR_CATCHALL_MAPPING (no default value)
9.1.3.12 Optin and Presence Attributes
1) Rewrote the first sentence to: The LDAP_OPTIN1 through LDAP_OPTIN8 MTA options specify LDAP attributes for per-user spam filter opt-in values based on destination addresses.
2) Added the following to first paragraph: LDAP_SOURCE_OPTIN1 through LDAP_SOURCE_OPTIN8 provide comparable originator-address-based per-user spam filter optins.
9.1.4 To Modify Group Membership Attribute Syntax New section.
Chapter 10, About MTA Services and Configuration
<c_channel>b_channel <d_channel>a_channel
10.3.1 File Format in the Mappings File
1) In entire chapter: <use_text_database> use_text_databases
2) <252> 256 and 1024 characters respectively. [The maximum size of a line in the mapping file is 4096.]
In entry for $E: [$+1E exits immediately without interpreting the rest of the template.]
In entry MAX_MESSAGES [The minimum value is 10.]
10.9 To Convert Addresses from an Internal Form to a Public Form
<NOTE: Messaging Server provides other facilities for address manipulation, such as the aliases file and specialized mapping tables. For best performance, however, rewrite rules should be used whenever possible to perform address manipulations. See Chapter 11, Configuring Rewrite Rules.>
[Messaging Server provides other facilities for address manipulation, such as the aliases file and specialized mapping tables. For best performance, however, rewrite rules should be used whenever possible to perform address manipulations. See Chapter 11, Configuring Rewrite Rules.]
Added. Completely new.
10.10.4.1 To Block Content Return on Large Messages
Appended at end:
[The MTA fetches the block limit associated with the envelope return address and will set RET=HDRS if no return policy is specified and the message size exceeds the block limit. This prevents nondelivery reports for large messages from being undeliverable themselves. No new options or settings are associated with this change.]
10.12 Optimizing MTA Performance. New section.
10.12.1 Optimizing Authorization Checks to the LDAP Directory for Messages Addressed to Mailing Lists. New section.
Chapter 11, Configuring Rewrite Rules
Added entry for $nT: Overrides the default ALIAS_MAGIC setting, where n is an appropriate value for the ALIAS_MAGIC MTA option. Overrides the setting for the domain when the rule matches during alias expansion.
Added entry for $. See manual.
Chapter 12, Configuring Channel Definitions
New Channels: addresssrs, caption, chunkingclient, chunkingserver, description, destinationspamfilterX, destinationsrs, disabledestinationspamfilterX, disablesourcespamfilterX, ignoremessageencoding, ignoremultipartencoding, interpretmessageencoding, interpretmultipartencoding, noaddresssrs, nochunkingclient, nochunkingserver, nodestinationsrs, nosourcesrs, sourcespamfilterX, sourcesrs.
New sections: 12.4.6 Support for SMTP Chunking, 12.6.20 Recipient Address Handling, 12.8.5 Interpreting Content-transfer-encoding Fields on Multiparts and Message/RFC822 Parts, 12.12.9 Set Channel Displays for Monitoring Framework
12.12.5 Spam Filter Keywords. Rewrote and added new keywords.
Chapter 13, Using Predefined Channels
tcp_local entry adds the following: [Sometimes tcp_local gets mail from remote SMTP hosts via proxy or firewall. tcp_local is also sometimes used for internal relay activities.]
Added a lot of new material including a new section Including Conversion Tag Information in Various Mapping Probes.
Chapter 14, Integrating Spam and Virus Filtering Programs Into Messaging Server
LDAP_optinX rewritten. LDAP_SOURCE_OPTINX added.
New entry for USERNAME_MAPPING.
To Specify User-level Filtering
New Note added to Step 1.
To Specify Domain-level Filtering. New Note added to Step 1.
14.7 Support for Sieve Extensions. New paragraph added (3rd from top).
<spamfilterX_config_file=/opt/SUNWmsgsr/lib/milter.opt> spamfilter1_config_file=/opt/SUNWmsgsr/lib/milter.opt
14.10 Other Anti-Spam and Denial-of-Service Technologies. New section.
14.10.1 Anti-Spam Technique: Delay Sending the SMTP Banner. New Section
Chapter 15, Handling Forged Email Using the Sender Policy Framework
15.7 Handling Forwarded Mail in SPF Using the Sender Rewriting Scheme (SRS). New Section
16.5.1 To Configure Back End Stores with LMTP and a Minimal MTA. Rewritten.
16.5.4 Handling 4.2.1 Mailbox Busy Error in Response to LMTP Message Data. New section
Chapter 17, Vacation Automatic Message Reply
17.4 Vacation Autoreply Attributes
New attribute definition: LDAP_AUTOREPLY_ADDRESSES
17.5.1 To Send Autoreply Messages for Email That Have Been Automatically Forwarded from Another Mail Server. New section.
Chapter 18, Mail Filtering and Access Control
New entry for $! (Available in FROM_ACCESS only). Disables the sending of vacation messages regarding this message; that is, it sets the novacation flag.
18.3.3 FROM_ACCESS Mapping Table
Added paragraph to end of section: [The $( metacharacter in a FROM_ACCESS specifies that an address should be read from the result string and used to replace the current overriding postmaster address. $) has the same effect with the added constraint that the overriding postmaster address must not be set prior to invoking the mapping. This allows for specific postmaster addresses to be used with addresses in nonlocal domains - domain postmaster addresses by definition only work with locally defined domains. The override address is (currently) the last string read from the FROM_ACCESS result prior to reading any $N/$F failure result.]
New Entry for $D: Causes an additional argument to be read from the template result after the mandatory SMTP auth rulset and realm, and optional application information addition. This value must be an integer with the same semantics as the BANNER_PURGE_DELAY value. That is, it specifies the number of centiseconds to delay before purging and sending the banner. A value of 0 disabled both the delay and purge. Note that any PORT_ACCESS mapping setting overrides the BANNER_PURGE_DELAY SMTP channel option. See Anti-Spam Technique: Delay Sending the SMTP Banner for details on using this anti-spam feature. $U [Selectively] enable channel level debugging.
18.3.6 To Limit Specified IP Address Connections to the MTA
First paragraph rewritten: To limit how often a particular IP address can connect to the MTA, see Chapter 19, Throttling Incoming Connections Using MeterMaid. Limiting connections by particular IP addresses can be useful for preventing excessive connections used in denial-of-service attacks. In the past, this function was performed using the shared library, conn_throttle.so in the Port Access mapping table. No new enhancements are planned for conn_throttle.so and MeterMaid is its more effective replacement.
Two new bullets:
-
Sieve redirect can now add three header fields:
resent-date: date-of-resend-operation resent-to: address-specified-in-redirect resent-from: address-of-sieve-owner
The new :resent and :noresent arguments to redirect can be used to control whether or not these fields are added. If neither argument is specific the system default is used. The system default is controlled by the new SIEVE_REDIRECT_ADD_RESENT MTAoption. Setting the option to 1 causes these fields to be generated unless :noresent used. A setting of 0 causes the fields to be generated only if :resent is used. The option defaults to 1, which means the fields are generated by default for regular redirects.
-
Sieve redirect has been enhanced with three new arguments:
:resetmailfrom - Reset the envelope FROM: address to that of the current Sieve owner.
:keepmailfrom- Preserve the envelope FROM: address from the original message.
:notify - Specify a new set of notification flags for the redirected message. A single parameter is required giving a list of notification flags. The same set of flags accepted by the NOTIFY parameter of the DSN SMTP extension are accepted here: SUCCESS, FAILURE, DELAY and NEVER. Note that these flags are specified as a Sieve list, for example:
redirect :notify ["SUCCESS","FAILURE"] "foo@example.com";
The default if :notify isn't specified as the normal SMTP default of FAILURE, DELAY.:keepmailfrom is the default unless :notify is specified, in which case the default switches to :resetmailfrom. The one additional exception is that specification of the SUCCESS flag forces the use of :resetmailfrom unconditionally.
Chapter 19, Throttling Incoming Connections Using MeterMaid
Rewritten for clarity. Also added two new sections:
19.4 Limit Excessive IP Address Connections Using Metermaid—Example and 19.4.1 Additional Useful MeterMaid Options
Chapter 20, Managing the Message Store
Changed three instances of store.overquotastatus to local.store.overquotastatus in Table 20–7and 20.8.4.4 To Enable or Disable Quota Enforcement.
20.14.1.4 Check stored Processes
<stored -t -v> imcheck
20.15 Migrating or Moving Mailboxes to a New System
This entire section was moved from Chapter 2, Upgrading from Messaging Server 5.2 to Sun Java System Messaging Server.
Chapter 21, Message Archiving No changes.
Chapter 22, Configuring the JMQ Notification Plug-in to Produce Messages for Message Queue
To Configure a JMQ Notification Plug-in.
<o Sun Java Messaging Server 6 2006Q3>
Chapter 23, Configuring Security and Access Control
For "End-user account configuration" bullet, <product (valid only for Sun LDAP Schema 1).>
Chapter 24, Administering S/MIME for Communications Express Mail
No substantive changes
25.3.1 Understanding the MTA Log Entry Format
Step 5: [The SMS channel can be configured to log a page count rather than file size in this field. See LOG_PAGE_COUNT.]
<P POP-before-SMTP via the MMP was used. P is added to the E record.>
25.3.3 Specifying Additional MTA Logging Options
<A value of 0 is the default and indicates that syslog (event log) logging is not performed.> [A value of 0 disables generation of the syslog notices. A non-zero value enables generation of the syslog notices, with the absolute value controlling the syslog priority and facility mask. (Positive values mean syslog notices and the regular mail.log* entries; negative values, which are not recommended, mean syslog notices only, disabling the regular mail.log* entries. A value of 0 is the default and indicates that syslog (event log) logging is not performed.]
To Control Formatting of Log Entries
1) Add to enqueue/dequeue attributes:
[qt - the amount of time a message has spent in the queue (LOG_QUEUE_TIME=1)]
2) Add to connection attributes: [ct - the amount of time a message has spent in the queue (LOG_QUEUE_TIME=1, also used in en entries)]
3) Updated the following MTA Logging examples:
25.3.4.5 MTA Logging Example – Sending to a Nonexistent Remote User
25.3.4.6 MTA Logging Example – Rejecting a Remote Side's Attempt to Submit a Message
25.3.4.7 MTA Logging Example – Multiple Delivery Attempts
25.3.4.8 MTA Logging – Incoming SMTP Message Routed Through the Conversion Channel — Outbound Connection Logging <process ID here is the same, 40a5> [process ID here is the same, 1f625] [10. The connection mailhub.sesta.com is closed now that the delivery of the message (dave in this example) is complete.]
25.3.4.10 MTA Logging Example: Inbound Connection Logging
1) [configutil -o local.msgtrace.active -v "msgtrace" In this command message trace information for all processes is written to the msgtrace log file]
2) Remove the next two sections: <To Redirect Message Tracing to a Single Log File> and <To Unconfigure Message Trace Loggings>
Chapter 26, Troubleshooting the MTA
26.2.4 Check that the Job Controller and Dispatcher are Running26.2.4 Check that the Job Controller and Dispatcher are Running
You could also use imsimta qm jobs to list, channel by channel, all active and pending delivery processing jobs currently being managed by the Job Controller. Additional cumulative information is provided for each channel such as the number of message files successfully delivered and those requeued for subsequent delivery attempts. The command syntax is as follows:
jobs [-[no]hosts] [-[no]jobs] [-[no]messages] [channel-name]
26.3.8.1 Diagnosing and Cleaning up .HELD Messages Rewritten.
Chapter 27, Monitoring Messaging Server
27.4.1.2 To Monitor the Size of the Message Queues
<use imsimta qm and imsimta summarize.> [use imsimta qm and imsimta summarize.]
Appendix A, SNMP SupportNo substantive changes
Appendix B, Administering Event Notification Service in Messaging Server No substantive changes.
Appendix C, Short Message Service (SMS)
Under Miscellaneous Options:
1) DEBUG - Default: <1>6
2) LISTEN_CONNECTION_MAX - Maximum number of concurrent, inbound TCP connections to allow across all SMPP relay and server instantiations. Default: 10,000
3) LOG_PAGE_COUNT - Controls the value recorded in the mail.log file's message size field to be page count instead of blocks. Default 0
New section for LOG_PAGE_COUNT.
Appendix D, Installation Worksheets No differences.
- © 2010, Oracle Corporation and/or its affiliates