Enabling Live Remote; Securing The Domain With Ssl Connections To The Mta - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

If a message file exceeds the delay message size, the message file is moved into the low
priority (6) message queue, where only one MTA thread is allocated to process very large
messages. This arrangement allows typical messages to be processed promptly, while delaying
large messages that exceed the specified size. The result is that large messages do not slow
down processing of typical messages. Message size restrictions override message priority,
meaning that even high priority messages are delayed if they exceed the size restrictions.
5 Click OK.
6 To exit the Link Configuration Tool and save your changes, click File > Exit > Yes.
ConsoleOne then notifies the MTA to restart using the new message size limits.
If a user's message is not sent out of the domain because of this restriction, the user receives an e-
mail message providing the following information:
Delivery disallowed - Transfer limit is nn MB
However, the message is delivered to recipients in the sender's own domain.
There are additional ways to restrict the size of messages that users can send, as described in
Section 12.3.5, "Restricting the Size of Messages That Users Can Send," on page

41.2.2 Enabling Live Remote

You can configure the MTA to redirect GroupWise Remote client requests to other MTAs and
POAs. The GroupWise client can establish a client/server connection to an MTA across the Internet,
eliminating the queuing and polling process used by earlier Remote clients. The result is improved
performance for Remote client users. To configure the MTA to redirect Remote client requests, add
the /liveremote, /lrconn and
remote connections from the MTA server console. See
page 669.
IMPORTANT: Live remote connections are still supported in GroupWise, but are not
recommended. Superior functionality is currently available by using proxy servers for POAs, so that
client users in Remote mode connect to their mailboxes through the proxy servers rather than
through MTAs. Full SSL security is provided through the proxy servers and POAs. See
Section 36.3.1, "Securing Client/Server Access through an External Proxy Server," on page

41.2.3 Securing the Domain with SSL Connections to the MTA

Secure Sockets Layer (SSL) ensures secure communication between the MTA and other programs
by encrypting the complete communication flow between the programs. For background
information about SSL and how to set it up on your system, see
and SSL Encryption," on page
To configure the MTA to use SSL:
1 In ConsoleOne, browse to and right-click the MTA object, then click Properties.
2 Click GroupWise > Network Address to display the Network Address page.
/lrwaitdata switches to the MTA startup file. You can monitor the live
1161.
"Displaying Live Remote Status" on
Section 75.2, "Server Certificates
195.
509.
Configuring the MTA 643