114 lines
7.6 KiB
HTML
114 lines
7.6 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="E-mail example: Send and receive e-mail locally" />
|
||
|
|
<meta name="abstract" content="This example demonstrates how e-mail is processed between local users." />
|
||
|
|
<meta name="description" content="This example demonstrates how e-mail is processed between local users." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzairgetstart.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzairemcommnd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzairpopverbs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzairplan.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzairscenariomailloc" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>E-mail example: Send and receive e-mail locally</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzairscenariomailloc"><a name="rzairscenariomailloc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">E-mail example: Send and receive e-mail locally</h1>
|
||
|
|
<div><p>This example demonstrates how e-mail is processed between local
|
||
|
|
users.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Situation</h4><p>Jane Smith, the Human Resources director,
|
||
|
|
needs to send a message to Sam Jones in the Legal department. They both work
|
||
|
|
at MyCompany headquarters. By following this process, you will be able to
|
||
|
|
see how e-mail is handled on your iSeries™ server.</p>
|
||
|
|
<p>The objectives
|
||
|
|
of this example are as follows:</p>
|
||
|
|
<p></p>
|
||
|
|
<ul><li>Demonstrate how e-mail clients and servers relate to each other, and how
|
||
|
|
a message is processed</li>
|
||
|
|
<li>Use the SMTP server to send mail</li>
|
||
|
|
<li>Deliver mail to a POP user</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Details</h4><p>The following image depicts the network
|
||
|
|
for MyCompany and how a mail message passes through the various layers in
|
||
|
|
order to get to its final destination. After the image, you will find a step-by-step
|
||
|
|
description of the path the mail message takes through this network.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. Sample network configuration</span><br /><img src="rzair501.gif" alt="Mail passing from sender to receiver in a local network" /><br /></div>
|
||
|
|
<p>Jane is using the Netscape mail client. She writes a message and
|
||
|
|
sends it to SamJones@mycompany.com.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Phase 1: SMTP client to SMTP server</h4><p>The SMTP client
|
||
|
|
on Jane's PC uses the configuration data that was entered for the outgoing
|
||
|
|
server and identity. The identity field is used for the <span class="uicontrol">From</span> address.
|
||
|
|
The outgoing server is the host that is contacted by the PC SMTP client. Because
|
||
|
|
the address is entered as a domain, the SMTP client queries Domain Name System
|
||
|
|
(DNS) to get the IP address of the SMTP server, and discovers that it is 192.1.1.8.</p>
|
||
|
|
<p>The
|
||
|
|
SMTP client now contacts the SMTP server on the SMTP port (Port 25 at 192.1.8).
|
||
|
|
The dialog that is used between the client and the server is the SMTP protocol.
|
||
|
|
The SMTP server accepts the delivery of the mail, and the message is transmitted
|
||
|
|
from the client to the server using TCP/IP.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Phase 2: SMTP server delivers the message to the POP server</h4><p>The
|
||
|
|
SMTP server tests the domain of the recipient to see if it is local. Because
|
||
|
|
it is local, the mail is written out to an IFS file and the QMSF Framework
|
||
|
|
Create Message application programming interface (API) is used to put the
|
||
|
|
message information in the QMSF queue. The QMSF framework allows the distribution
|
||
|
|
of e-mail, calling exit programs or snap-ins to handle specific mail types.
|
||
|
|
The message information identifies Sam's address as SMTP format, so the framework
|
||
|
|
calls the SMTP Address Resolution exit program. This program again checks
|
||
|
|
that the message is local. Because it is local, it uses the system distribution
|
||
|
|
directory (data entered through WRKDIRE) to find the recipient's SMTP address.
|
||
|
|
It finds Sam's address, and finds the mail service level is system message
|
||
|
|
store in the directory entry for this user, therefore it recognizes it as
|
||
|
|
a POP account. Then SMTP Address Resolution adds his profile information to
|
||
|
|
the message information. It marks the information as POP local delivery. The
|
||
|
|
QMSF Framework then calls the POP Local Delivery exit program, which finds
|
||
|
|
the profile information and the name of the IFS file and delivers the mail
|
||
|
|
to Sam's mailbox.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Phase 3: POP Client retrieves message for Sam Jones from the
|
||
|
|
POP server</h4><p>Some time later, Sam decides to use his mail client (Netscape)
|
||
|
|
to check his mailbox for e-mails. The POP client on his PC is configured to
|
||
|
|
check the POP server at mycompany.com for the user name SamJones and password
|
||
|
|
(******). The domain name is again changed to an IP address (using DNS). The
|
||
|
|
POP client contacts the POP server using the POP port and the POP3 protocol.
|
||
|
|
The mailbox user name and password are used by the POP server on the iSeries to
|
||
|
|
check that the user name and password match the profile and password of an iSeries user.
|
||
|
|
After it is validated, the profile name is used to find Sam's mailbox. The
|
||
|
|
POP client loads the message, and sends a request back to the POP server to
|
||
|
|
delete the mail from the POP mailbox. The message is then displayed in Netscape
|
||
|
|
for Sam to read.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzairgetstart.htm" title="You can learn the concepts and procedures for configuring and administering e-mail on your iSeries server.">E-mail</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzairplan.htm" title="Before setting up e-mail, you should have a basic plan for how you will be using e-mail on your iSeries server.">Plan for e-mail</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzairemcommnd.htm" title="Simple Mail Transfer Protocol (SMTP) is a TCP/IP protocol used in sending and receiving e-mail. It is typically used with POP3 or Internet Message Access Protocol to save messages in a server mailbox and download them periodically from the server for the user.">Simple Mail Transfer Protocol</a></div>
|
||
|
|
<div><a href="rzairpopverbs.htm" title="The Post Office Protocol (POP) Version 3 mail interface is defined in Request for Comments (RFC) 1725. RFC is the mechanism used to define evolving Internet standards.">Post Office Protocol</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|