Version 5.1
E-mail |
|---|
| ||||||||
|
|
Version 5.1 |
||||||||||||||||||||||||||||||
|
|
The CommuniGate Pro Server transfers messages to the following destinations:
All messages are created as temporary files. They are stored in the Queue directory as files with the .tmp extension. A module or an internal component stores the message envelope and the message itself in such a file and then submits it to the Enqueuer component for processing.
The message envelope is a set of text lines. Each line specifies either the message return-path, or one message recipient address, or message delivery options.
If a module fails to compose a message (for example, an SMTP connection breaks during message transfer), the module discards of the temporary file.
When a message is completely composed and submitted to the Enqueuer, the file extension is changed to .msg and the message is scheduled for processing.
When the Server restarts, the Enqueuer component finds all files with the .msg extension stored in the Queue directory and resubmits them for processing.
Open the General pages in the Settings realm of the CommuniGate Pro WebAdmin Interface, and find the Temp File Manager panel panel on the Others page:
The Temporary Files manager Log records are marked with the TEMPFILE tag.
If a Server is heavily loaded, it can contain thousands of message files in its Queue directory. Many operating and file systems cannot efficiently process large directories. You may want to split the Queue directory into several subdirectories, each containing a portion of Temporary and Queue files.
You may want to limit the total number of messages in the CommuniGate Pro Queue. When this number is reached, the modules reject attempts to submit new messages.
Use the WebAdmin Interface to specify the Queue processing options. Open the Mail pages in the Settings realm, then open the Queue page:
When a message is submitted for processing, the Enqueuer component examines its envelope information. Each recipient address is parsed and passed to the Router component. The Router component decides which module or component should process each recipient address.
When all recipient addresses are parsed and routed, the Enqueuer component applies the Server-Wide Rules to the message. Then it passes the message to the modules specified with the Router component.
Communication modules do not process E-mail messages immediately, but enqueue them into the module-specific queues. The SMTP module creates and maintains a queue for each Internet domain, the Local Delivery module creates and maintains a queue for each local Account, etc.
The Enqueuer component can enqueue messages:Most of the internal components enqueue messages asynchronously, as they cannot do anything useful if a message is rejected with the Enqueuer component. The components receiving messages directly from users or remote systems (SMTP, MAPI, WebMail, XIMSS) try to enqueue messages synchronously, so if a message is rejected with the Enqueuer component, the submitting agent (a user or a remote system) can get an error message.
Use the WebAdmin Interface to configure the Enqueuer component. Open the Queue page in the Settings realm.
You should increase the number of Enqueuer processors if:
When a communication module fails to transfer a message, it uses the kernel queue management component to delay processing.
When a communication module transfers a message or when it rejects a message because of a fatal error, it removes the message from the module queue. The module composes a delivery report and passes it to the Dequeuer component.
The Dequeuer component processes delivery information. If requested, it composes Delivery Status Notification (DSN) messages and submits them back to the system for delivery to the original message sender. When a message has several recipients, the Dequeuer component may choose to delay DSN generation, so each DSN message can contain reports about several recipients.
When all message recipients are processed and the message is dequeued from all queues, the Dequeuer component removes the message file from the Queue directory.
Use the WebAdmin Interface to configure the Dequeuer component. Open the Queue page in the Settings realm.
| everybody | reports are generated and sent whenever the message sender requests them. |
| clients | reports are generated and sent if the sender has submitted the message from a Client IP Address or if the message has been submitted by an authenticated user. |
| authenticated | reports are generated and sent if the message has been submitted by an authenticated user (via WebUser, XIMSS, SMTP AUTH, MAPI, etc.) |
| nobody | positive reports are not generated. |
Transfer modules (such as SMTP, Local Delivery, LIST, and PIPE) maintain one or several queues for messages to be delivered. Each module uses its own methods to build the queues (for example, the SMTP module usually builds a separate queue for each remote domain to deliver to, while the Local Delivery module builds a separate queue for each local Account), see the manual section describing the module for more details.
To open a module queue, click the queue name link on module Monitor page. The module ("host") queue page opens:
The table contains a record for each message in the queue. For each enqueued message, the following information fields are displayed:
If you have the Can Release Queues access right, and the Queue has the Delayed status, the Host Queue Monitor page contains the Release Now button. Click this button to remove the delay interval set for this queue and to allow the module to process the queue immediately.
If you have the Can Reject Queues access right, and the Queue has the Delayed or Ready status, the Host Queue Monitor page contains the Reject Host Queue button. Click this button to reject the queue:
The specified text is used to generate DSN messages (error reports) for all messages placed into this queue.
If the Suppress Failed Delivery Reports option is selected, no DSN message is generated when the queue messages are being rejected.
To monitor the status of a message in the Server Queue, click the message link on the Module queue or other Monitor page. The Message Monitor page opens:
The first part of the page shows the message attributes: the envelope Return-Path, Message-ID, Envelope-ID (if present), message Subject, and the time the message was submitted to the Server Queue.
The second part of the page lists all active message recipient addresses (if a message address has been already processed, it is not shown). For each address the following information is displayed:
If you have the Can Reject Queues access right, the Message Monitor page contains the Reject Message button. Click this button to reject all active message addresses.
Only the addresses that are not being processed can be rejected.
The specified text is used to generate DSN messages (error reports) for all rejected recipient addresses.
If the Suppress Failed Delivery Reports option is selected, no DSN message is generated when the message addresses are being rejected.