Unable to send or receive email


A common issue that users experience with the Email Engine is that they cannot send or receive email. A simple way to troubleshoot this issue is to verify that you have configured your incoming and outgoing mailboxes correctly.

Testing your incoming mailbox

If you are unable to test your incoming mailbox configuration successfully, verify the following conditions:

  • The Email Engine is running.
  • The mail server is running.
  • The Status field of the mailbox is set to Enabled.
  • The email account used by the Incoming Mailbox is a valid account on the mail server (POP3 or IMAP4 or EWS), or the Exchange profile specified for this mailbox is accessible on the system the Email Engine is running on (MAPI).

    Note

    By default, the Email Engine service is launched as the local system account. However, if you opted to configure a MAPI mailbox during installation, you must change the login information (in the Services control panel) for the Email Engine service from the local system account to the appropriate account.

  • The port number in the mailbox entry is the correct port number for communicating with your mail server.
  • You entered the correct password for the email account in the Incoming Mailbox Basic configuration tab (POP3 or IMAP4 or EWS).
  • The email address you chose to send the message to was the correct address for directing email to the email account (POP3 or IMAP4 or EWS) or profile (MAPI) specified in the Incoming Mailbox.
  • You waited for a period of time not less than that indicated by the polling interval before checking the AR System Email Messages form for your message.

    Important

    The Email Engine might not immediately recognize changes you make to your mailbox in an effort to troubleshoot possible configuration issues. For more information, see Changing-the-default-time-interval.

Testing your outgoing mailbox

If you are unable to test your outgoing mailbox configuration successfully, verify the following conditions:

  • The Email Engine is running.
  • The mail server is running.
  • The Status field of the mailbox is set to Enabled.
  • Determine if the mail server requires authentication for messages to be sent. If your mail server requires authentication, then you must make sure that you have provided valid email account information for this mail server in the Basic Configuration tab for this mailbox (SMTP or EWS) or the name of a valid Exchange profile (MAPI).
  • The port number in the mailbox entry is the correct port number for communicating with your mail server.
  • You entered the correct password for the email account in the Outgoing Mailbox Basic configuration tab (SMTP or EWS) or you logged in to the system as the domain user account that has permission to use the Microsoft Exchange profile (MAPI).
  • You waited for a period of time not less than that indicated by the polling interval before checking the AR System Email Messages form to see if your message was sent.

Configuring a watcher thread for Email Engine

You can also configure a watcher thread for Email Engine. A watcher thread monitors the outgoing email messages. 

  • Configure a watcher thread by using the com.bmc.arsys.emaildaemon.EnableWatcherThread  parameter. 
  • Configure the time interval for the watched thread by using the com.bmc.arsys.emaildaemon.WatcherThreadInterval parameter in Centralized Configuration. 

For more information, see Configuration-settings-C-D.

CCS-Screenshot.png
When an email message is not processed for five minutes, which is the default time interval, the watcher thread stops the Email Engine process. On Windows, Email Engine restarts the Email Engine service.

Email Engine restart resolves issues that might occur due to a thread that is stuck.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*