Domino server Tasks

The Domino server runs several tasks to carry out various types of user requests:
 Administration process: Runs as the AdminP task. This task automates the
administrative activities, such as renaming a user or server, creating replicas on multiple
servers, and moving user mail files on the server.
 Agent manager: Runs as the AMGR task. This task runs the agents on the server.
 Billing: Runs as the BILLING task. This task collects the billing information in the Billing
database.
 Calendar connector: Runs as the CALCONN task. The CALCONN task connects to
another server to retrieve the free time information about the users and resources on
that server when a user tries to look up this information.
 Cataloger: Runs as the CATALOG task. This task updates the database catalog on the
server with information about the databases present on that server.
 Certificate authority process: Runs as the CA task. This task automates server CA-
based activities, such as registering users or servers from the Web.
 Collector: Runs as the COLLECT task. This task collects statistics from the Domino
servers and logs them into the Monitoring Results database.
 Compactor: Runs as the COMPACT task. This task compacts the databases on the
server. You can also use this task to update an older version of a database to the latest
On Disk Structure (ODS).
 DECS server: Runs as the DECS task. This task allows real-time access to back end
enterprise databases, such as Oracle or Sybase.
 Designer: Runs as the DESIGN task. This task updates all the databases on the server
that are based on templates using the design changes in the template.
 DIIOP server: Runs as the DIIOP task. This task allows Java applets or Java-based
programs to access the Domino data remotely using Common Object Request Broker
Architecture.
 Directory cataloger: Runs as the DIRCAT task. This task populates and updates the
directory catalogs on the server.
 Domain indexer: Runs as the DOMIDX task. This task creates a central, full-text index
for all specified databases and file systems in a domain for domain wide searching.
 Event monitor: Runs as the EVENT task. This task monitors the events on the server.
You configure these events in the Monitoring Configuration database.
 Fixup: Runs as the FIXUP task. This task fixes the corrupt documents and views in a
database.
 HTTP web server: Runs as the HTTP task. This task configures the Domino servers a
Web server and allows Web clients, such as browsers, to access the Domino server.
 IMAP mail server: Runs as the IMAP task. This task allows the IMAP-based clients to
access their messages on the Domino server.
 Internet cluster manager: Runs as the ICM task. This task provides fail over and
workload balancing to the HTTP clients that access the Domino Web server.
 ISpy: Runs as the runjava ISpy task. This task sends probes to other servers or users to
monitor connectivity.
 LDAP server: Runs as the LDAP task. This task enables the Domino server to provide
directory services to the LDAP clients.
 Maps extractor: Runs as the MAPS task. This task creates and updates the connection
topology maps for replication and mail routing in the Domino Administrator client.
 Message tracking collector: Runs as the MTC task. This task collects the information
about the messages on a server and stores them in the Message Tracking Store
database. You use this information to track messages on a server and to generate mail
usage reports.
 Object store manager: Runs as the OBJECT task. This task manages the databases
and user mail files that use shared mail.
  POP3 mail server: Runs as the POP3 task. This task allows POP3 mail clients to
access the Domino server to download their messages.
 Replicator: Runs as the REPLICATOR task. This task replicates databases between
servers.
 Router: Runs as the ROUTER task. This task routes messages to users and servers.
 Run Java: Runs as the RUNJAVA task. This task runs Java-based server add-in tasks,
such as ISpy and the Change Manager.
 Schedule manager: Runs as the SCHED task. This task collects the information when a
user updates the calendar or books a resource and updates this information in the Free
Time database.
 SMTP server: Runs as the SMTP task. This task allows Domino to transfer messages to
the Internet.
 Stats: Runs as the STATS task. This task generates statistics for a remote server, on
demand.
 Web retriever: Runs as the WEB task. This task retrieves the Web pages for Domino
users, converts them into Notes documents, and stores them in the Web Navigator
database.
Problem
IBM Lotus Domino SMTP servers heavily rely on DNS for routing mail. Incorrectly configured and/or
general DNS related issues can interrupt the ability of Domino to send and receive Internet (SMTP)
mail. This document is intended to highlight frequently asked questions and answers regarding mail
routing issues, particularly SMTP mail routing issues.

Solution
Your Domino server is unable to receive any inbound SMTP mail. What should you check first?
You should confirm that the SMTP Listener task is active by issuing the command "Show Tasks" on
the server console. If "SMTP Listener task" does not appear in task list, issue the command "Load
SMTP" on the server console. At that point, if SMTP does not load as expected, check the Server
document to ensure the "SMTP listener task" is enabled.

You have confirmed that the SMTP task is running on the server. What else should you check?
In order for Domino to receive inbound SMTP mail, the appropriate DNS records must exist for your
domain. The Mail Exchange (MX) record is used to identify the mail server that is responsible for
accepting mail for your domain. If more than one mail server will be used in your environment, each
of these servers would require their own MX record. You can use NSLookup to confirm the correct
address exists for your inbound Domino SMTP mail server. If you do not find the appropriate MX
records, or you find an MX record that contains incorrect information for your server, contact your
ISP or DNS administrator.

How to Use NSLookup to Verify DNS (#1084986)

Using NSLookup to Troubleshoot DNS and SMTP Mail Issues (# 7006840 )

Your Domino server appears to have stopped routing mail and large amounts of mail are marked as
"pending" in the MAIL.BOX. How can you determine why this is happening?
You can start by issuing the command "Tell Router Show Queue" on the server console. This
command will report the status of each pending message including when the Router task will next
attempt to route mail. If the output shows "Last error: Server not responding", then the destination
server is most likely unavailable. To confirm, you can attempt to connect to Port 25 of the
destination server ( i.e., the "next hop" server) via Telnet.
If the "Tell Router Show Queue" output shows "Last error: Waiting for DNS", then the problem is
likely with the DNS server being used by Domino. Try running NSLookup from a command prompt
on the Domino server to see if you can establish a connection with the DNS server. Running
NSLookup will allow you to remove Domino from the picture and confirm the status of the DNS
server. If you receive "DNS request time out" errors, you should notify your DNS administrators as
the error is indicative of a problem with either your DNS server, or network connectivity to the DNS
server.

How to Use NSLookup to Verify DNS (#1084986)

Using NSLookup to Troubleshoot DNS and SMTP Mail Issues (# 7006840 )
Using Telnet to Troubleshoot SMTP Mail Issues (#7006824 )
Is there a workaround if DNS service is unavailable? (#1094598) What is the algorithm used by the
Router to route messages that failed to route initially?
(#1089949)

Outbound SMTP mail is not routing and the error "Router: No route found to domain" appears on
the server console. What should you do?
Verify that the server in question is properly configured to send outbound SMTP mail. To do so, open
the server's Configuration Settings document and select the Router/SMTP -> Basics tab. Make sure
the "SMTP allowed outside the local internet domain" field is set to "Enabled". You should note that,
however, Domino servers can actually utilize multiple Configuration Settings documents (also
referred to as Server Configuration documents). Configuration Settings documents can be created
for individual servers, all servers (indicated by an asterisk - *), and for groups of servers. For tips
on how to determine which Configuration Settings document is used by a particular server, refer to
the technote titled "When there are multiple Configuration Settings documents, which one takes
precedence?" (#1095933).
Domino is unable to send any outbound SMTP mail to a particular Internet domain. What could be
the cause of this issue?
This type of issue is typically seen when the receiving host (i.e., the receiving server) is configured
to perform reverse lookup. When reverse lookup is configured on SMTP servers, the server will
attempt to look up the connecting server's IP address in DNS prior to allowing the connection. If the
connecting server ( e.g., your Domino server) does not have a pointer (PTR) record in DNS, then
the connection will be denied. Thus, no mail from your Domino server can route to that particular
receiving host. Nonetheless, Domino is not the cause of the problem; rather, it is the lack of
appropriate DNS records for the machine on which Domino is running. To resolve this type of issue,
contact your DNS Administrator to confirm the appropriate DNS records exist for your domain. For
information on a similar issue where a DNS server stopped responding to client requests, refer to
the technote titled " Messages Fail to Route to some Internet Domains Due to DNS Errors with
Microsoft Windows Server 2003" (# 1165647).
Are there any tools that can be used to troubleshoot DNS issues?
Yes. There are various Web-based DNS tools available for that purpose. For an example of such a
tool, refer to the technote titled " Determining if a mail domain uses reverse DNS entries for MX
records" (# 1159351). By using external Web-based tools, you can utilize the DNS servers
accessible on the Web application instead of those on your local machine. This can be especially
helpful if you suspect that the DNS entries within your domain are experiencing problems.
Since upgrading the operating system on the Domino server from Windows NT to Windows 2000 or
Windows 2003, neither NRPC nor SMTP mail will route successfully. What could be the cause of this
issue?
With the release of Windows 2000, Microsoft changed the way DNS Name Servers are recorded in
the Windows Registry and the key that is used to store this information. Administrators now have
the ability to specify different DNS Name Servers to use on a per network interface card level.
Whereas in Windows NT 4.0, the DNS Name Server entry would be used for all network interface
cards on the server. The problem reported most often is that immediately following an upgrade to
Windows 2000 or Windows 2003, no mail routes outbound or to other Domino servers. To resolve
this issue, you should ensure that the registry key indicated below is properly configured: