Release 5.2
A86653-01
 Library |
 Service |
 Index |
| Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
You can install an SMTP gateway to provide access to other mail systems such as Sendmail, the most common mail transfer agent included with most major UNIX-based Internet hosts that handle e-mail routing.
Configuring a gateway includes the following topics discussed in this chapter:
You must have at least one SMTP gateway running in your system so that your users can send e-mail to each other. You can use the Configuration Assistant to create your first gateway after you install a node.
You can also create a gateway manually using the following procedure.
When you create a gateway, eMail Server creates both an incoming and an outgoing gateway process. For example, if your gateway is called GWY1, it would have the processes GWY1_IN for incoming mail, and GWY1 for outgoing mail.
After creating the gateway, you must perform the following tasks manually to complete the gateway configuration:
This task can be done automatically by using the Configuration Assistant, or it can be done manually by using the Administration Tool GUI or the OOMGR command-line interface.
(Create).
You will use the gateway name and password that you specify here when create the gateway configuration file (unx.cfg). If you do not specify a password, the default is welcome.
The new gateway appears under Gateways in the navigation tree. If you expand the new gateway, you will see the two gateway processes that were created. These processes also appear under Nodes > node_name > Processes > Instances > gateway_instance.
IOFCMGR>insert gateway name=<gateway_name> node=<node_name> kind=SMTP
After you create a gateway, you must create a gateway configuration file, unx.cfg, to specify the gateway name and password as well as the connect string for the database so that the gateway can access the eMail Server database. Each set of incoming and outgoing gateway processes needs a separate configuration file.
Before creating the gateway configuration file, you must create a gateway. Refer to "Creating an SMTP Gateway" for instructions.
This task must be done manually using a text editor.
$ORACLE_HOME/office/config/node_sid/unx.cfg
gateway password connect_string
Add one line per node in the system. The first connect_string is used to fetch the gateway parameters. The following connect_strings are used to deliver mail. The gateway tries to determine the home node for the recipient and delivers the mail directly to that node. If it cannot determine the home node or if the mail is addressed to recipients on multiple nodes, the mail is delivered to the default node. The default node is specified by the second connect_string in the config file. If there is only one connect_string in the file, then it is used for both fetching parameters and delivering mail.
|
See Also:
"Creating an SMTP Gateway" for more information if you do not know the gateway name and password |
After creating the gateway configuration file, you must register the gateway with Sendmail, the standard UNIX mail transfer agent that handles all messages traveling to and from the Internet. To register the gateway with Sendmail, you must specify gateway information in the sendmail.cf file so that Sendmail knows how to forward messages coming in from the Internet.
Before registering the SMTP/MIME gateway with Sendmail, you should complete the following tasks:
This task must be done manually using a text editor.
Mofcmail, [tab] P=<$ORACLE_HOME>/bin/ofcuto, F=rlSsDCFMPpmn, S=10, R=20,
[tab]A=ofcuto - <$ORACLE_HOME> <ORACLE_SID> -f <config_file> - $g $a $b $f $x ( $u )
| Replace | With |
|---|---|
|
|
This tells Sendmail to run the eMail Server mailer. The mailer delivers the message to the Gateway process, which then inserts the message in the eMail Server database. You may want to specify a different mailer name. See the Sendmail documentation for more information about mailers. |
|
|
Enter the full path for your $ORACLE_HOME directory. |
|
<ORACLE_SID> |
Enter the value for Oracle sid of your database. |
|
|
Press the Tab key where indicated by [tab] instead of the space bar. |
|
|
Name of the gateway configuration file. The default filename is unx.cfg.See Also: "Creating the SMTP Gateway Configuration File" for more information about the SMTP gateway configuration file |
## eMail Server: Hook to eMail Server mailer ## R$+.ofcmail[tab][tab]$#ofcmail $:$1[tab]{tab]eMail Server passoff
or
## eMail Server: Hook to eMail Server mailer ## R$+.OFCMAIL[tab][tab]$#ofcmail $:$1[tab][tab]eMail Server passoff
T root daemon uucp <eMail Server_owner>
$ /usr/lib/sendmail -bz
On Windows NT, refer to the Windows NT documentation for instructions.
On Solaris, use the following procedure:
If the sendmail configuration file is set up as described in "Registering the SMTP Gateway with Sendmail", then incoming messages must be addressed using the following format:
userid.mailer_name@domain
To address messages using the standard Internet naming conventions (userid@domain), you can create an alias for each user ID that maps the user ID to userid.mailer_name. To do this add the following line to the end of sendmail alias file (usually /etc/mail/aliases):
userid: userid.mailer_name
| Variable | Description |
|---|---|
|
|
User name of the eMail Server user as defined in the eMail Server directory. Refer to "Displaying a Directory Entry" for instructions on finding user names. |
|
|
Name of the mailer specified in the Sendmail.cf file. If you use the example provided in step 2 of "Registering the SMTP Gateway with Sendmail", the mailer name is |
|
Note: If you do not use the procedure in "Registering the SMTP Gateway with Sendmail" to configure the gateway for Sendmail, then you may need to use another procedure for setting up aliases. For documentation on Sendmail, go to the Sendmail Web site at
|
You can create rewriting rules to redirect message routing and to manage addressing details, such as gateways. Rewriting rules search for addresses containing certain patterns of characters and modify the addresses in some way. These rules are used primarily to interpret messages sent through the Internet.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
|
See Also:
"Guidelines for Creating Gateway Rewriting Rules" for more information about performing this task |
(Create).
"Parameters for Creating Gateway Rewriting Rules" for more information about the parameters in this dialog box
See Also:
IOFCMGR>insert rule ruleno=<rule_number> 2>pattern=<pattern> 3>result=<result> 4><description>;
|
See Also:
"Parameters for Creating Gateway Rewriting Rules" for more information about the parameters available with this command |
To create a pair of rules that leave correct addresses untouched and add the necessary gateway name to incorrect addresses, you might create the following rules:
ruleno=10 pattern=%:% result=%0:%1 description=any address that already specifies SMTP: is left the way it is ruleno=20 pattern=%@% result=SMTP.anywhere.com:%0@%1 description=any address that has @ gets SMTP:anywhere.com added to the beginning
<gateway_name>:<foreign_address>
| Parameter | Description |
|---|---|
|
< |
Name of the gateway process entered when creating the gateway record. See "Creating an SMTP Gateway" for more information. |
|
< |
SMTP mailbox address of the recipient. This must adhere to the rules governing SMTP mail addresses. |
For example, if the name of the gateway is unix2.domain1 and the SMTP mailbox of the recipient address is jsmith@acme.com, you would address the message:
unix2.domain1:jsmith@acme.com
suffix .mailer_name (the name you assigned the SMTP/MIME gateway mailer in the sendmail.cf file) must be added to the user's username. If you use the example provided in step 2 of "Registering the SMTP Gateway with Sendmail", the mailer name is ofcmail, and you would use the following format for the user name:
<username.ofcmail>@<internet_address>
The eMail Server SMTP/MIME Gateway supports Japanese, Chinese, and Korean multibyte character encoding for incoming and outgoing mail.
To configure the character encoding for SMTP/MIME gateway, you must perform the following tasks:
Modify the ExecArguments parameter value, -n nls-lang, for the incoming gateway process to specify the language that you want the gateway to support.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
'-f <config_file> -n <nls_lang>'
|
See Also:
"Variables for Configuring the Gateway for Multibyte Support" for more information about the parameters in this dialog box |
IOFCMGR>modify process server=<gateway_name_in.text> 2>instance=<instance_number> to execarguments='-f <config_file> 3>-n <nls_lang>';
|
See Also:
"Variables for Configuring the Gateway for Multibyte Support" for more information about the parameters available with this command |
| Variable | Description |
|---|---|
|
(Optional) |
Name of the gateway configuration file (optional). See Also: "Creating the SMTP Gateway Configuration File" for more information about this file |
|
< |
Name of the inbound gateway. |
|
(OOMGR only) |
Instance of the gateway to process incoming mail. |
|
< |
NLS_LANG value consisting of three parts: language, territory, and character set. The syntax is: For example: See Also:"Supported Languages and Character Sets" for a complete list of Asian languages and character sets supported |
After creating a gateway, you need to modify the following three process parameters of the SMTP/MIME gateway:
default_charset, the default encoding type for outbound and inbound messages
default_textencoding, the default encoding type of message encoding
default_hdrencoding, the default encoding type for the MIME header
Refer to "Specifying Multi-value Parameters" for instructions on how to ____.
default_charset iso-2022-JP
default_textencoding 7bit
default_hdrencoding B (B specifies base64 and Q indicates quoted-printable.)
The following table lists the database character sets and the character encoding for Japanese, Chinese, and Korean languages that are supported by the SMTP/MIME gateway.
If you want to run multiple gateways on one node to distribute the workload or specify different parameters for different gateways such as the language parameters, then you must register and configure additional instances of the gateway process. This procedure assumes that you've already registered and configured one gateway process.
See Also:
execarguments='-f <config_file>'
Refer to "Setting a Parameter for a Registered Process" for instructions.
When you install an SMTP/MIME Gateway, you register the gateway with sendmail, the standard UNIX mail transfer agent. If you want to remove a gateway from your eMail Server system, you must deregister the gateway before deleting it. Deregistering the gateway removes the gateway's processes. If you do not deregister the gateway, ghost processes will continue. These processes must then be stopped manually. The Administration Tool automatically deregisters before deleting the gateway.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
(Remove).
IOFCMGR> deregister gateway name=<gateway_name>
IOFCMGR> delete gateway name=<gateway_name>
Messages being sent through the gateway can be stored in either encoded, or decoded format. This is important of you want to support the S/MIME standard for verifying the authenticity of a client. You can specify this format by modifying the store_body parameter.
Decoded format means that a message is broken down into parts, such as the header and body, decoded, and then stored in different database tables. Most clients understand how to retrieve decoded messages from these tables. However, if you are supporting S/MIME, messages with digital signatures will lose their signatures so authentication verification cannot happen.
Encoded format means that the gateway stores the message exactly as it is received in encoded format. This preserves encryption and digital signatures for S/MIME, but this format is currently only understood by the IMAP4 and POP3 protocol servers. Other clients may not be able to retrieve these messages.
You also have the option to save messages in both encoded and decoded formats to support all types of clients, but this can significantly increase the amount of database space used to save messages.
|
See Also:
|
You can configure Sendmail 8.8 or higher to reject unwanted junk mail (spam) from e-mail addresses and domains that you specify. When you do this, the unwanted messages are not delivered and are automatically returned to the sender.
This task must be done manually using a text editor.
For example:
ckent@acme.com llane@acme.com jolsen@acme.com
For example:
acme.com acme-pro.com junkmail.com
#Files to keep spammers information F{SpamDomains} /etc/mail/SpamDomains F{Spammers} /etc/mail/Spammers
############################################### ############# STOP THE SPAMMERS ############# ############################################### Scheck_mail R$={Spammers} $#error $@ 5.7.1 $: "550 We don't accept junk mail" R<$={Spammers}> $#error $@ 5.7.1 $: "550 We don't accept junk mail" R<$={Spammers}.> $#error $@ 5.7.1 $: "550 We don't accept junk mail" R$* $: $>3 $1 R$*<$*@$={SpamDomains}.>$* $#error $@ 5.7.1 $: "550 We don't accept junk mail from your domain" R$*<$*@$={SpamDomains}>$* $#error $@ 5.7.1 $: "550 We don't accept junk mail from your domain"
On Windows NT, see the Windows NT documentation for instructions.
On Solaris:
You can configure Sendmail 8.8 or higher to prevent junk-mail senders from using your server machine as a mail relay to forward unwanted spam messages by only delivering messages to or from a local machine.
This task must be done manually using a text editor. There are two methods for completing this task.
For example:
Cw acme us.acme.com acme-sun acme-sun.us.acme.com
Scheck_rcpt R$* [tab] $: $>3 $1 R$+<@$=w>$* [tab] $@ok R$+<@$=w.>$* [tab] $@ok R$+<@$=w.LOCAL>$* [tab] $@ok R$* [tab] $#error $@ 5.7.1 $: [tab] "550 we do not support relaying"
On Windows NT, see the Windows NT documentation for instructions.
On Solaris:
An internal machine will be considered as an outsider by the gatekeeper. eMail Server uses a more complicated check_rcpt rule set example to handle this situation:
For example:
130.35.9 130.35.10 127.0.0.1
F{LocalIP} /etc/mail/LocalIP
Scheck_rcpt # first: get client addr R$+ [tab] $: $(dequote "" $&{client_addr} $) $| $1 R0 $| $* [tab] $@ ok [tab] no client addr: directly invoked R$={LocalIP [tab] $* $| $* [tab] $@ ok # not local, check rcpt R$* $| $* [tab] $: $>3 $2 # remove local part, maybe repeatedly R$+ [tab] $:$>removelocal $1 # still something left? R$*<@$+>$* [tab] $#error $@ 5.7.1 $: 550 we do not support relay Sremovelocal # remove RelayTo part (maybe repeatedly) R$*<@$=w>$* [tab] $: $>removelocal $>3 $1 $3 R$*<@$=w.LOCAL>$* [tab] $: $>removelocal $>3 $1 $3 R$*<@$*>$* [tab] $@ $1<@$2>$3 # dequote local part R$- [tab] $: $>3 $(dequote $1 $) R$*<@$*>$* [tab] $: $>removelocal $1<@$2>$3
On Windows NT, see the Windows NT documentation for instructions.
On Solaris:
If you are using virus-checking software with Sendmail, configure it as necessary.
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|