Configuring POP, IMAP, and HTTP Services

compared with
Current by shjorth_sun
on Jul 12, 2009 23:02.

(show comment)
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (25)

View page history
{{configutil -o service.pop.numprocesses -v}} _number_
To enable POP over SSL:
To enable POP over SSL on port 995:
{noformat}
# ./configutil -o service.pop.enablesslport -v 1
# ./configutil -o service.pop.sslusessl -v 1
# ./configutil -o service.pop.sslport -v 995
# ./stop-msg pop
# ./start-msg pop
{noformat}
 
{code}
configutil -o service.pop.enablesslport -v 1
configutil -o service.pop.sslport -v 995
{code}
TLS is also supported if SSL is configured correctly.
{{configutil -o service.imap.banner -v}} _banner_
To enable IMAP over SSL on port 993:
{noformat}
# ./configutil -o service.imap.enablesslport -v 1
# ./configutil -o service.imap.sslusessl -v 1
# ./configutil -o service.imap.sslport -v 993
# ./stop-msg imap
# ./start-msg imap
{noformat}
h3. Configuring IMAP IDLE
* The Webmail Server no longer must be installed on each back-end server.
* The Webmail Server can serve as a front-end server performing the multiplexing capabilities previously performed by Messenger Express Multiplexor (MEM).
* MEM is obsoleted and is no longer used.
* The Messenger Express Multiplexor (MEM) is obsolete and is no longer used.
* On the client side, nothing is changed except that users can now access shared folders that are not on their message store.
For each IMAP server that users access, the Webmail Server needs to know the IMAP port, whether to use SSL, and the admin credentials to use for user log-in. The {{configutil}} parameters to do this are as follows:
{{local.service.proxy.imapport\[.}}_hostname_{{\]}} — -- IMAP port on which to connect (default 143).
 
{{local.service.proxy.imapssl}} — -- Enable SSL (default no).
 
{{local.service.proxy.admin\[.}}_hostname_{{\]}} — -- Admin ID.
 
{{local.service.proxy.adminpass\[.}}_hostname_{{\]}} — -- Admin password.

These parameters can be set globally (applying to every IMAP back-end server), or for each individual IMAP back-end server by appending the back end's fully qualified domain name to the option name.
To use IMAP over SSL, {{mshttpd}} must be also configured as an SSL HTTP server, and the {{mshttpd}} certificate database must trust the IMAP back end's CA. You must enable {{service.httpt.sslusessl}}. If the back-end message store running IMAP is using a self-signed certificate (for example, as created by {{generate-certDB}}), then this certificate needs to be added to the front-end {{mshttpd}} daemon server.

Note that if {{local.service.proxy.admin/pass}} isn't set, logins will be rejected with the error "_Mail server unavailable. Administrator, check server log for details._" and the HTTP log will list the missing configuration options.
To enable or disable the HTTP service:
{{configutil -o}} {{service.http.enable -v \[ -o service.http.enable -v}} {{\[ yes | no \]}}

By default, the HTTP service sends outgoing web mail to the local MTA for routing or delivery. You might want to configure the HTTP service to send mail to a remote MTA, for example, if your site is a hosting service and most recipients are not in the same domain as the local host machine. To send web mail to a remote MTA, you need to specify the remote host name and the SMTP port number for the remote host. To specify the port number:
{{configutil -o}} {{service.http.port -v}} _number_

To enable a separate port for HTTP over SSL:
{{configutil -o}} {{service.http.enablesslport -v \[ -o service.http.enablesslport -v}} {{\[ yes | no \]}}

To specify a port number for HTTP over SSL:
{{configutil -o}} {{service.http.sslport -v}} _number_

To enable or disable password login:
{{configutil -o}} {{service.http.plaintextmincipher -v}} _value_

If _value_ is greater than 0, then disable use of plaintext passwords unless a security layer (SSL or TLS) is activated. This forces users to enable SSL or TLS on their client to login which prevents exposure of their passwords on the network. Default is 0.
To set the maximum number of network connections per process (for more information, see [#Number of Connections per Process]):
{{configutil -o}} {{service.http.maxsessions -v}} _number_ (for more information, see [#Dropping Idle Connections]):

To set the maximum idle time for client sessions (for more information, see [#Logging Out HTTP Clients]):
{{configutil -o}} {{service.http.sessiontimeout -v}} _number_

To set the maximum number of threads per process:
{{configutil -o}} {{service.http.maxthreads -v}} _number_

To set the maximum number of processes:
{{configutil -o}} {{service.http.numprocesses -v}} _number_

When an HTTP client constructs a message with attachments, the attachments are uploaded to the server and stored in a file. The HTTP service retrieves the attachments and constructs the message before sending the message to an MTA for routing or delivery. You can accept the default attachment spool directory or specify an alternate directory. You can also specify a maximum size allowed for attachments. To specify the attachment spool directory for client outgoing mail use the following command. Note that this includes all the attachments encoded in base64, and that base64 encoding requires an extra 33 percednt more space. Thus a 5 Mbyte limit in the parameter results in the maximum size of one message and attachments being about 3.75 Mbyte.
{{configutil -o}} {{service.http.spooldir -v}} _dirpath_

To specify the maximum message size:
{{configutil -o}} {{service.http.maxmessagesize -v}} _size_

where _size_ is a number in bytes. Note that this includes all the attachments encoded in base64, and that base64 encoding requires an extra 33 percent more space. Thus a 5 Mbyte limit in the parameter results in the maximum size of one message and attachments being about 3.75 Mbytes.
To specify an alternate MTA host name:
{{configutil -o}} {{service.http.smtphost -v}} _hostname_

To specify the port number for the alternate MTA host name:
{{configutil -o}} {{service.http.smtpport -v}} _portnum_

To enable HTTP access over SSL on port 8991:
{noformat}
# ./configutil -o service.http.enablesslport -v 1
# ./configutil -o service.http.sslusessl -v 1
# ./configutil -o service.http.sslport -v 8991
# ./stop-msg http
# ./start-msg http
{noformat}

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact