postoffice for groupwise

8/9/2019 PostOffice For GroupWise

1/16

Post Office Access Mode: Client/ServerStage : 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 ClientThe GroupWise client uses TCP/IP protocol to communicate the

message to the Post Office Agent (POA).

Stage : POA in Local Post OfficeThe 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.DB file) assigned to the sender.

Creates a pointer in the sender's user database (USER.DB file) so the message appears in the sender's Mailbox.

Places attachments larger than 2 KB in the \OFFILES\FD 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 OfficeThe POA also performs the following actions for the recipient:

Creates a pointer in each recipient's user database (USER.DB file) to the message in the message database

(MSG.DB file) so the message appears in the recipient's Mailbox.

Updates the message in the message database (MSG.DB file) with a "Delivered" status for each recipient.

Stage : POA in Local Post OfficeThe POA uses TCP/IP protocol to communicate to the GroupWise client that a new message has arrived.

Stage : Recipient's GroupWise ClientThe Notify component of the recipient's GroupWise client notifies the recipient that a new message has arrived.
http://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.html


2/16

Stage : RecipientEach recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise ClientEach recipient's GroupWise client uses TCP/IP protocol to communicate the "Opened" status to the POA.

Stage : POA in Local Post OfficeThe 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 OfficeThe POA uses TCP/IP protocol to communicate the "Opened" status to the sender's GroupWise client.

Stage : SenderWhen 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 : SenderThe 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 ClientThe GroupWise client performs the following actions for the sender:
http://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.htmlhttp://www.novell.com/documentation/gw52/tb300003.html


3/16


Creates a pointer in the sender's user database (USER.DB file) so the message appears in the sender's Mailbox.

Places attachments larger than 2 KB in the \OFFILES\FD 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 OfficeThe POA also performs the following actions for the recipient:

Creates a pointer in each recipient's user database (USER.DB file) to the message in the message database

(MSG.DB file) so the message appears in the recipient's Mailbox.

Updates the message in the message database (MSG.DB file) with a "Delivered" status for each recipient.



Stage : Recipient's GroupWise ClientEach recipient's GroupWise client updates the message in the message database with an "Opened" status for

that recipient.

Stage : SenderWhen 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).
http://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300004.htmlhttp://www.novell.com/documentation/gw52/tb300004.html


4/16

Post Office Delivery Mode: Use App Thresholds (notexceeded)

Stage : SenderThe 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 ClientThe GroupWise* client performs the following actions for the

sender:

Adds the message to the message database (MSG.DB

file) assigned to the sender.

Creates a pointer in the sender's user database

(USER.DB file) so the message appears in the sender's

Mailbox.

Places attachments larger than 2 KB in the \OFFILES\FD 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 ClientThe GroupWise client performs the following actions for each recipient:

Updates each recipient's user database (USER.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.DB file) with a "Delivered" status for each

recipient.



Stage : Recipient's GroupWise Client
http://www.novell.com/documentation/gw52/tb300005.htmlhttp://www.novell.com/documentation/gw52/tb300005.htmlhttp://www.novell.com/documentation/gw52/tb300005.htmlhttp://www.novell.com/documentation/gw52/tb300005.htmlhttp://www.novell.com/documentation/gw52/tb300005.htmlhttp://www.novell.com/documentation/gw52/tb300005.html


5/16

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

that recipient.

Stage : SenderWhen 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).
http://www.novell.com/documentation/gw52/tb300005.html


6/16

Post Office Delivery Mode: Client Delivers Locally

Stage : SenderThe 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 ClientThe GroupWise client performs the following actions for the

sender:


Creates a pointer in the sender's user database (USER.DB file) so the message appears in the sender's

Mailbox.

Places attachments larger than 2 KB in the \OFFILES\FD subdirectory assigned to thesender and creates pointers from the message to its attachments. (For database efficiency, messages and


Stage : Sender's GroupWise ClientThe GroupWise client performs the following actions for each recipient:

Updates each recipient's user database (USER.DB file) so the message appears in each recipient'sMailbox 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.DB file) with a "Delivered" status for each

recipient.


Stage : Recipient
http://www.novell.com/documentation/gw52/tb300006.htmlhttp://www.novell.com/documentation/gw52/tb300006.htmlhttp://www.novell.com/documentation/gw52/tb300006.htmlhttp://www.novell.com/documentation/gw52/tb300006.htmlhttp://www.novell.com/documentation/gw52/tb300006.html


7/16

Each recipient opens the message in the GroupWise client.

Stage : Recipient's GroupWise ClientEach recipient's GroupWise client updates the message in the message database with an "Opened" status for

that recipient.


http://www.novell.com/documentation/gw52/tb300006.htmlhttp://www.novell.com/documentation/gw52/tb300006.html


8/16

Access between Post Offices: TCP/IP Link

Stage : SenderThe 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 ClientThe GroupWise* client performs the following actions for the sender:



Mailbox.

http://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tbook3.html


9/16



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 Diagramsfor alternative message flows within the

post office.

Stage : MTA in Sender's Post OfficeThe 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. SeeMTA Local Directory.

Stage : TCP/IP Module in Sender's Post OfficeThe 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 DomainThe TCP/IP transport module in the domain places the message into the input queue for the MTA in the

domain.

Stage : MTA in Local DomainThe MTA in the domain routes the message into the holding queue for the recipient's post office.

Stage : TCP/IP Module in Local DomainThe 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 OfficeThe 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 OfficeThe MTA in the recipient's post office transfers the message into the input queue for the POA in the recipient's

post office.


connect the post office to the domain. SeeMTA Local Directory.
http://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.html


10/16

Stage : POA in Recipient's Post OfficeThe 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.DB file) corresponding to the one assigned to the

sender.

Creates a pointer in the recipient's user database (USER.DB file) so the message appears in therecipient'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 \OFFILES\FD 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 ClientEach 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 OfficeThe 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.


connect the post office with the domain. SeeMTA Local Directory.

Stage : TCP/IP Module in Recipient's Post OfficeThe 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 DomainThe 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
http://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tbook403.html


11/16

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 DomainThe 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 OfficeThe 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 linksconnect the post office to the domain. SeeMTA Local Directory.

Stage : POA in Sender's Post OfficeThe POA in the sender's post office updates the sender's message database (MSG.DB file) with the

"Delivered" status information (and possibly "Opened" as well if the recipient has opened the message).


http://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tb300007.htmlhttp://www.novell.com/documentation/gw52/tbook403.html


12/16

Access between Post Offices: Direct

Stage : SenderThe user sends a message to recipients in a different post office in the same domain.





Creates a pointer in the sender's user database (USER.DB file) so the message appears in the sender'sMailbox.







post office.

http://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.html


13/16

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.




sender.

Creates a pointer in the recipient's user database (USER.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 \OFFILES\FD subdirectory corresponding to



Creates a "Delivered" status message in the appropriate priority 0-7 subdirectory of the recipient's MTA inputqueue.





Stage : MTA in Local DomainThe 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 OfficeThe POA in the sender's post office updates the sender's message database (MSG.DB file) with the



http://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.htmlhttp://www.novell.com/documentation/gw52/tb300008.html


14/16

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.






Mailbox.







post office.

http://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tbook3.htmlhttp://www.novell.com/documentation/gw52/tbook3.html


15/16

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.




sender.

Creates a pointer in the recipient's user database (USER.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 \OFFILES\FD subdirectory corresponding to



Creates a "Delivered" status message in the appropriate priority 0-7 subdirectory of the recipient's MTA input

queue.





Stage : MTA in Local DomainThe 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
http://www.novell.com/documentation/gw52/tbook403.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tb300009.htmlhttp://www.novell.com/documentation/gw52/tbook403.html


16/16

The POA in the sender's post office updates the sender's message database (MSG.DB file) with the



http://www.novell.com/documentation/gw52/tb300009.html

postoffice for groupwise

Documents