Siebel Email Administration Guide > Troubleshooting Siebel Email Response >

About Investigating and Reporting Processing Abnormalities


Communications Inbound Receiver and Communications Inbound Processor do not stop if an incoming work item (such as an email or a phone call) causes abnormal behavior during processing. Instead, a log file entry is created for the abnormal behavior. An example of abnormal behavior is a missing From address in an email.

The log files are:

  • Comminboundrcvr.log for Communications Inbound Receiver
  • Comminboundprocessor_xxxxx.log for Communications Inbound Processor

To investigate abnormal behavior during processing, access the Administration - Communications screen, Communications Inbound Events, and then the Components view and make sure entries exist for each email that is processing. After an email is successfully processed, the entry is deleted. If the email is not successfully processed, then make sure that the status and comments are correct. Also check the URL to make sure that the name is correct. For information about resubmitting a failed email for processing, see Resubmitting Failed Email.

Before reporting any abnormal behavior during processing, make sure CommInboundRcvr and CommInboundProcessor are set to the proper debugging level and MIME message. Attach both of these files to the abnormal behavior when reporting the issue.

Siebel Email Administration Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.