imaccessd

imaccessd provides email clients with access to the Sun Internet Mail Server. The imaccessd daemon supports two access protocols: Post Office Protocol, version 3 (POP3, RFC 1939); and Internet Message Access Protocol (IMAP, RFC 2060). The imaccessd daemon process normally runs whenever the mail server is up. Unlike other commands, imaccessd is a daemon which, when started, runs in the background. If this daemon is not running, all client requests for IMAP or POP connections receive a "Connection Refused" error.

---

Note - You must be logged in as root to use imaccessd.

---

Syntax

imaccessd [ -d ] [-l config_file_location] [ -p service=port ] [ -t thread_limit ] [ -v ]

The following options are used with imaccessd:

-d	Turn debugging mode on.
-l config_file_location	Location of the Message Access Services configuration file (ims.cnf). If the -l option is not specified, the default location (/etc/opt/SUNWmail/ims/) will be used.
-p service=port	Specifies the port to be monitored. service must be either pop3, imap, pop3s, or imaps (SSL); port must be a numerical TCP port number. If the -p option is not specified, the monitoring defaults to support both IMAP and POP3 on their standard services port numbers. Multiple -p options can be used. The ports specified by the -p option override the defaults in /etc/services. When port=0 the service should be disabled.
-t thread_limit	Specifies the maximum number of threads per process. thread_limit defaults to 50, and rarely needs to be redefined.
-v	Write detailed (verbose) diagnostic messages to the debug log.

In the event that a fault occurs in a thread in imaccessd, this thread is terminated and a timestamped core file is created in /var/opt/SUNWmail/ims/adm/corefiles. This core file should be sent to SunSoft to help diagnose the problem that occurred and to improve the reliability of future versions of SIMS. Up to 10 core files can be created during the lifetime of the imaccessd parent process.

After a fault in a thread, the files opened by this thread are closed, and the client whose connection was terminated should be able to reconnect immediately. To limit side effects of the fault, the process containing the faulted thread continues with the other threads, but is not used for new incoming connections.

The imaccessd process should never be killed using the kill -9 command. To kill the process, use the kill command without the -9 argument--this kills the parent process. If kill -9 is used, run imcheck -c before restarting imaccessd.

---

Note - imaccessd is normally started and stopped with the im.server script (/etc/init.d)

---

Examples

To provide normal IMAP service only on Sun's usual IMAP debugging port, use the following command:

# imaccessd -p imap=145

The following command will disable IMAP:

# imaccessd -p imap=0