This message flow diagram shows how outbound messages travel through the GroupWise directory structure to the Internet when there is a TCP/IP link between the MTA and the GWIA and when the GWIA can communicate successfully with the Internet host to which the message is addressed.
Stage |
Icon |
Description |
---|---|---|
Sender |
|
The user sends a message to recipients across the Internet by providing their Internet addresses. In this diagram, the access mode setting for the local post office is Client/Server Only. |
Sender’s GroupWise Client |
|
The GroupWise client communicates the message to the POA by way of TCP/IP. |
POA for Sender’s Post Office |
|
The POA receives the message from the GroupWise client and performs the following actions for the sender:
|
POA for Sender’s Post Office |
|
The POA then communicates the message to the MTA for the sender’s domain by way of TCP/IP, and deletes the copy in the MTA input queue because the TCP/IP transfer to the MTA was successful. |
MTA for Sender’s Domain |
|
The MTA for the sender’s domain receives the message and places it into the MTA “in progress” (gwinprog) queue. |
MTA for Sender’s Domain |
|
The MTA determines that the message must be sent out across the Internet. Because there is a TCP/IP link between the MTA and the GWIA, the MTA creates a copy of the message in the appropriate priority 0-7 subdirectory of the GWIA hold queue (mslocal/mshold/gatewayx/0-7), in case the TCP/IP link to the GWIA is currently closed. |
MTA for Sender’s Domain |
|
The MTA then communicates the message to the GWIA for the sender’s domain by way of TCP/IP, and deletes the copy in the GWIA holding queue because the TCP/IP transfer to the GWIA was successful. |
GWIA for Sender’s Domain |
|
The GWIA receives the message and places it into the MTA output queue (wpcsout/gwid/0-7) on behalf of the MTA. The MTA output queue is the GWIA input queue. |
GWIA for Sender’s Domain |
|
The GWIA scans its input queues according to the setting on the Gateway Time Settings page of the GWIA object in ConsoleOne. The GWIA picks up the file in binary-encrypted format from the wpcsout/gwid/0-7 directory and converts it. The GWIA encodes the message in MIME format with the appropriate encoding scheme. When the message file is built, the GWIA saves it with S as the first character of the file name and places the message file in the domain/wpgate/gwia/send directory for processing. |
GWIA for Sender’s Domain |
|
While the GWIA is processing the message file in the send directory, it changes the first character of the file name to P. When processing is completed, the GWIA sends the message to the destination host across the Internet. |
GWIA for Sender’s Domain |
|
If the GWIA receives a 250 OK SMTP reply code from the destination Internet host, it places a Transferred status message into the input queue of the MTA for the sender’s domain in case the TCP/IP link to the GWIA is currently closed. |
GWIA for Sender’s Domain |
|
The GWIA then communicates the Transferred status message to the MTA for the sender’s domain by way of TCP/IP, and deletes the copy in the MTA input queue because the TCP/IP transfer to the MTA was successful. |
MTA for Sender’s Domain |
|
The MTA for the sender’s domain receives the Transferred status message and places it into the MTA “in progress” (gwinprog) queue for processing. |
MTA for Sender’s Domain |
|
The MTA for the sender’s domain communicates the Transferred status message to the POA for the sender’s post office by way of TCP/IP. |
POA for Sender’s Post Office |
|
The POA for the sender’s post office updates the sender’s message database (msgnnn.db) with the Transferred status information. |
POA for Sender’s Post Office |
|
The POA for the sender’s post office communicates the Transferred status to the sender’s GroupWise client by way of TCP/IP. |
Sender |
|
When the sender checks the sent items in his or her mailbox in the GroupWise client, the message displays the Transferred status because the GWIA was able to sent it successfully. |