Post Office Access Mode: Client/Server

Stage : Sender

The user sends a message to recipients in the same post office. The
Access Mode setting for the post office is Client/Server. Therefore,
the GroupWise* client communicates with the post office by way
of TCP/IP.

Stage : Sender's GroupWise Client

The GroupWise client uses TCP/IP protocol to communicate the

message to the Post Office Agent (POA).

Stage : POA in Local Post Office

The POA receives the message by way of TCP/IP from the

GroupWise client and performs the following actions for the sender:

Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the sender and
creates pointers from the message to its attachments. (For database efficiency, messages and recipient lists larger than 2
KB are also handled as attachments.)

Stage : POA in Local Post Office

The POA also performs the following actions for the recipient:

Creates a pointer in each recipient's user database (USER<xxx>.DB file) to the message in the message database
(MSG<0-24>.DB file) so the message appears in the recipient's Mailbox.
Updates the message in the message database (MSG<0-24>.DB file) with a "Delivered" status for each recipient.

Stage : POA in Local Post Office

The POA uses TCP/IP protocol to communicate to the GroupWise client that a new message has arrived.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.
 Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client uses TCP/IP protocol to communicate the "Opened" status to the POA.

Stage : POA in Local Post Office

The POA receives the "Opened" status by way of TCP/IP from the GroupWise client and updates the message in the
message database with the "Opened" status for each recipient who opens the message.

Stage : POA in Local Post Office

The POA uses TCP/IP protocol to communicate the "Opened" status to the sender's GroupWise client.

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of "Delivered" for each
recipient (and possibly "Opened" as well if the recipient has opened the message).

Post Office Delivery Mode: Use App Thresholds (exceeded)

Stage : Sender

The user sends a message to recipients in the same post office. The
delivery mode setting for the post office is to Use App Thresholds, and
the threshold is exceeded.

Because the threshold is exceeded, the POA will write to the recipients'
databases instead of the GroupWise* client to return control to the client
user more quickly. However, the GroupWise client still writes to the
sender's databases.

Stage : Sender's GroupWise Client

The GroupWise client performs the following actions for the sender:
 Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the sender and
creates pointers from the message to its attachments. (For database efficiency, messages and recipient lists larger than 2
KB are also handled as attachments.)
Creates a copy of the message in the appropriate priority 0-7 subdirectory of the POA input queue.

Stage : POA in Local Post Office

The POA also performs the following actions for the recipient:

Creates a pointer in each recipient's user database (USER<xxx>.DB file) to the message in the message database
(MSG<0-24>.DB file) so the message appears in the recipient's Mailbox.
Updates the message in the message database (MSG<0-24>.DB file) with a "Delivered" status for each recipient.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client updates the message in the message database with an "Opened" status for
that recipient.

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of "Delivered" for each
recipient (and possibly "Opened" as well if the recipient has opened the message).
Post Office Delivery Mode: Use App Thresholds (not
exceeded)
Stage : Sender

The user sends a message to recipients in the same post office.

The delivery mode for the post office is set to Use App
Thresholds, but the threshold is not exceeded.

Stage : Sender's GroupWise Client

The GroupWise* client performs the following actions for the

sender:

Adds the message to the message database (MSG<0-24>.DB

file) assigned to the sender.
Creates a pointer in the sender's user database
(USER<xxx>.DB file) so the message appears in the sender's
Mailbox.
Places attachments larger than 2 KB in the <post
office>\OFFILES\FD<0-7F> subdirectory assigned to the
sender and creates pointers from the message to its attachments. (For database efficiency, messages and
recipient lists larger than 2 KB are also handled as attachments.)

Stage : Sender's GroupWise Client

The GroupWise client performs the following actions for each recipient:

Updates each recipient's user database (USER<xxx>.DB file) so the message appears in each recipient's
Mailbox and updates the notification information in the user database so the recipient can be notified of the
message.
Updates the message in the message database (MSG<0-24>.DB file) with a "Delivered" status for each
recipient.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client updates the message in the message database with an "Opened" status for
that recipient.

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of
"Delivered" for each recipient (and possibly "Opened" as well if the recipient has opened the message).
Post Office Delivery Mode: Client Delivers Locally

Stage : Sender

The user sends a message to recipients in the same post office.

The delivery mode for the post office is set to Client Delivers
Locally. Therefore, the GroupWise* client updates the
databases of all recipients.

When a user sends a message to a large number of recipients,

the user may experience a pause while the GroupWise client
updates the databases. If the pause is unacceptable, set the
delivery mode for the post office to Use App Thresholds.

Stage : Sender's GroupWise Client

The GroupWise client performs the following actions for the

sender:

Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's
Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the
sender and creates pointers from the message to its attachments. (For database efficiency, messages and
recipient lists larger than 2 KB are also handled as attachments.)

Stage : Sender's GroupWise Client

The GroupWise client performs the following actions for each recipient:

Updates each recipient's user database (USER<xxx>.DB file) so the message appears in each recipient's
Mailbox and updates the notification information in the user database so the recipient can be notified of the
message.
Updates the message in the message database (MSG<0-24>.DB file) with a "Delivered" status for each
recipient.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient
Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client updates the message in the message database with an "Opened" status for
that recipient.

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of
"Delivered" for each recipient (and possibly "Opened" as well if the recipient has opened the message).
Access between Post Offices: TCP/IP Link

Stage : Sender

The user sends a message to recipients in a different post office in the same domain.

In this diagram, the delivery mode in the local post office is set to Use App Thresholds and the threshold is not
exceeded. See Message Flow Diagrams for alternative message flows within the post office.

Stage : Sender's GroupWise Client

The GroupWise* client performs the following actions for the sender:

Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's
Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the
sender and creates pointers from the message to its attachments. (For database efficiency, messages and
recipient lists larger than 2 KB are also handled as attachments.)
Creates a copy of the message in the appropriate priority 0-7 subdirectory of the sender's MTA input queue.

If a different delivery mode were in effect in the post office, some or all of these actions would be performed by
the POA instead of the GroupWise client. See Message Flow Diagrams for alternative message flows within the
post office.

Stage : MTA in Sender's Post Office

The MTA in the sender's post office routes the message to the input queue for the TCP/IP transport module in
the post office.

An MTA, with its associated MSLOCAL directory structure, is required in each post office where TCP/IP links
connect the post office with the domain. See MTA Local Directory.

Stage : TCP/IP Module in Sender's Post Office

The TCP/IP transport module in the sender's post office communicates the message to the TCP/IP transport
module in the domain.

Stage : TCP/IP Module in Local Domain

The TCP/IP transport module in the domain places the message into the input queue for the MTA in the
domain.

Stage : MTA in Local Domain

The MTA in the domain routes the message into the holding queue for the recipient's post office.

Stage : TCP/IP Module in Local Domain

The TCP/IP transport module in the domain picks up the message and communicates it to the TCP/IP transport
module in the recipient's post office.

Stage : TCP/IP Module in Recipient's Post Office

The TCP/IP transport module in the recipient's post office places the message into the input queue for the MTA
in the recipient's post office.

Stage : MTA in Recipient's Post Office

The MTA in the recipient's post office transfers the message into the input queue for the POA in the recipient's
post office.

An MTA, with its associated MSLOCAL directory structure, is required in each post office where TCP/IP links
connect the post office to the domain. See MTA Local Directory.
 Stage : POA in Recipient's Post Office

The POA polls its input queue regularly. When it detects a new message, the POA in the recipient's post office
performs the following actions:

Adds the message to the message database (MSG<0-24>.DB file) corresponding to the one assigned to the
sender.
Creates a pointer in the recipient's user database (USER<xxx>.DB file) so the message appears in the
recipient's Mailbox and updates the notification information in the user database so the recipient can be notified
of the message.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory corresponding to
the one assigned to the sender and creates pointers from the message to its attachments. (For database
efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
Creates a "Delivered" status message in the appropriate priority 0-7 subdirectory of the recipient's MTA input
queue.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client creates an "Opened" status message in the appropriate priority 0-7
subdirectory of the recipient's MTA input queue.

Stage : MTA in Recipient's Post Office

The MTA in the recipient's post office routes the status response to the input queue for the TCP/IP transport
module in the post office.

An MTA, with its associated MSLOCAL directory structure, is required in each post office where TCP/IP links
connect the post office with the domain. See MTA Local Directory.

Stage : TCP/IP Module in Recipient's Post Office

The TCP/IP transport module in the recipient's post office communicates the message to the TCP/IP transport
module in the domain.

Stage : TCP/IP Module in Local Domain

The TCP/IP transport module in the domain places the status response into the input queue for the MTA in the
domain.

Stage : MTA in Local Domain

The MTA in the domain routes the status response into the holding queue for the sender's post office.

Stage : TCP/IP Module in Local Domain

The TCP/IP transport module in the domain picks up the status response and communicates it to the TCP/IP
transport module in the sender's post office.

Stage : TCP/IP Module in Sender's Post Office

The TCP/IP transport module in the sender's post office places the status response into the input queue for the
MTA in the sender's post office.

Stage : MTA in Sender's Post Office

The MTA in the sender's post office transfers the status response into the input queue for the POA in the
sender's post office.

An MTA, with its associated MSLOCAL directory structure, is required in each post office where TCP/IP links
connect the post office to the domain. See MTA Local Directory.

Stage : POA in Sender's Post Office

The POA in the sender's post office updates the sender's message database (MSG<0-24>.DB file) with the
"Delivered" status information (and possibly "Opened" as well if the recipient has opened the message).

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of
"Delivered" for each recipient (and possibly "Opened" as well if the recipient has opened the message).
Access between Post Offices: Direct

Stage : Sender

The user sends a message to recipients in a different post office in the same domain.

In this diagram, the delivery mode in the local post office is set to Use App Thresholds and the threshold is not
exceeded. See Message Flow Diagrams for alternative message flows within the post office.

Stage : Sender's GroupWise Client

The GroupWise* client performs the following actions for the sender:

Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's
Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the
sender and creates pointers from the message to its attachments. (For database efficiency, messages and
recipient lists larger than 2 KB are also handled as attachments.)
Creates a copy of the message in the appropriate priority 0-7 subdirectory of the sender's MTA input queue.

If a different delivery mode were in effect in the post office, some or all of these actions would be performed by
the POA instead of the GroupWise client. See Message Flow Diagrams for alternative message flows within the
post office.

Stage : MTA in Local Domain

The MTA polls its input queue as specified by the Scan Cycle setting in Agent Settings in NetWare*
Administrator. When it detects a new message, the MTA picks up the message from the sender's post office and
transfers it to its output queue in the recipient's post office. The MTA output queue is the input queue for the
POA in the recipient's post office.

Stage : POA in Recipient's Post Office

The POA polls its input queue regularly. When it detects a new message, the POA in the recipient's post office
performs the following actions:

Adds the message to the message database (MSG<0-24>.DB file) corresponding to the one assigned to the
sender.
Creates a pointer in the recipient's user database (USER<xxx>.DB file) so the message appears in the
recipient's Mailbox and updates the notification information in the user database so the recipient can be notified
of the message.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory corresponding to
the one assigned to the sender and creates pointers from the message to its attachments. (For database
efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
Creates a "Delivered" status message in the appropriate priority 0-7 subdirectory of the recipient's MTA input
queue.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client creates an "Opened" status message in the appropriate priority 0-7
subdirectory of the recipient's MTA input queue.

Stage : MTA in Local Domain

The MTA polls its input queue as specified by the Scan Cycle setting in NetWare Administrator. When it
detects a status response, the MTA picks it up from the recipient's post office and transfers it to its output queue
in the sender's post office. The MTA output queue is the input queue for the POA in the sender's post office.

Stage : POA in Sender's Post Office

The POA in the sender's post office updates the sender's message database (MSG<0-24>.DB file) with the
"Delivered" status information (and possibly "Opened" as well if the recipient has opened the message).

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of
"Delivered" for each recipient (and possibly "Opened" as well if the recipient has opened the message).
Access between Post Offices Blocked: Delivery Delayed

Stage : Sender

The user sends a message to recipients in a different post office in the same domain.

In this diagram, the delivery mode in the local post office is set to Use App Thresholds and the threshold is not
exceeded. See Message Flow Diagrams for alternative message flows within the post office.

Stage : Sender's GroupWise Client

The GroupWise* client performs the following actions for the sender:

Adds the message to the message database (MSG<0-24>.DB file) assigned to the sender.
Creates a pointer in the sender's user database (USER<xxx>.DB file) so the message appears in the sender's
Mailbox.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory assigned to the
sender and creates pointers from the message to its attachments. (For database efficiency, messages and
recipient lists larger than 2 KB are also handled as attachments.)
Creates a copy of the message in the appropriate priority 0-7 subdirectory of the sender's MTA input queue.

If a different delivery mode were in effect in the post office, some or all of these actions would be performed by
the POA instead of the GroupWise client. See Message Flow Diagrams for alternative message flows within the
post office.

Stage : MTA in Local Domain

The MTA polls its input queue as specified by Scan Cycle in Agent Settings in NetWare* Administrator. When
it detects a new message, the MTA picks up the message in the sender's post office. However, because the
recipient's post office is blocked, the MTA cannot complete the delivery. Therefore, the MTA stores the
message in its holding queue for the recipient's post office. See MTA Local Directory.

When the recipient's post office is open again, the MTA transfers the delayed message from the post office
holding queue to the MTA output queue in the recipient's post office. The MTA output queue is the input queue
for the POA in the recipient's post office.

Stage : POA in Recipient's Post Office

The POA polls its input queue regularly. When it detects a new message, the POA in the recipient's post office
performs the following actions:

Adds the message to the message database (MSG<0-24>.DB file) corresponding to the one assigned to the
sender.
Creates a pointer in the recipient's user database (USER<xxx>.DB file) so the message appears in the
recipient's Mailbox and updates the notification information in the user database so the recipient can be notified
of the message.
Places attachments larger than 2 KB in the <post office>\OFFILES\FD<0-7F> subdirectory corresponding to
the one assigned to the sender and creates pointers from the message to its attachments. (For database
efficiency, messages and recipient lists larger than 2 KB are also handled as attachments.)
Creates a "Delivered" status message in the appropriate priority 0-7 subdirectory of the recipient's MTA input
queue.

Stage : Recipient's GroupWise Client

The Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.

Stage : Recipient

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise Client

Each recipient's GroupWise client creates an "Opened" status message in the appropriate priority 0-7
subdirectory of the recipient's MTA input queue.

Stage : MTA in Local Domain

The MTA polls its input queue as specified by Scan Cycle in Agent Settings in NetWare* Administrator.

When it detects a new status response, the MTA picks it up in the recipient's post office. Because the sender's
post office is open, the MTA can immediately transfer the status response to the MTA output queue in the
sender's post office.

The MTA output queue is the input queue for the POA in the sender's post office.

Stage : POA in Sender's Post Office

The POA in the sender's post office updates the sender's message database (MSG<0-24>.DB file) with the
"Delivered" status information (and possibly "Opened" as well if the recipient has opened the message).

Stage : Sender

When the sender checks his or her Mailbox in the GroupWise client, the message displays a status of
"Delivered" for each recipient (and possibly "Opened" as well if the recipient has opened the message).