Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
Environment:
All Versions / Mailbox Configuration
Resolution:
Oracle B2C Service includes several features that allow you to break email loops:
Automatically Discard Auto-Response Email: You can have a mailbox automatically filter out some auto-reply email messages. The Discard Automatic Responses field for the mailbox can be set to Off, Conservative, Moderate or Aggressive. The default setting is Conservative, so you may need to increase this setting to reduce the chance of email loops. In order to set the Discard Automatic Responses field to a different value, go to Configuration > Site Configuration > Mailboxes, click the Incoming Email button in the ribbon, and use the Discard Automatic Responses drop-down menu (or Discard Filters tabs) to select the appropriate setting.
The filters used in each of the menu options (Conservative, Moderate, and Aggressive) are defined in the EGW_AR_CONS_*_FLTR, EGW_AR_MODR_*_FLTR, and EGW_AR_AGGR_*_FLTR configuration settings. You can configure the header and body filters separately for each menu option by editing the corresponding configuration setting.
Path to setting(s): Select Configuration from the navigation area > Site Configuration > Configuration Settings > and search by Key.
Prevent Mailbox from Sending Email to Itself: The EGW_LOOP_PREVENT_ENABLED configuration setting allows you to prevent an Oracle B2C Service mailbox from sending messages to itself. When EGW_LOOP_PREVENT_ENABLED is set to Yes, any email where the reply-to email address matches the reply-to email address of any mailbox in Oracle B2C Service will be discarded and no incident will be created. In this way, the mailbox deletes any messages from itself, which can prevent continuous email loops. By default, this setting is enabled (set to Yes). Note: The "reply-to" and "from" addresses can not match the "reply-to" and/or "from" address of any other existing mailbox.
Limit Amount of Email from an Address for a Specified Time Period: You can set configuration settings to allow a specified number of emails within a specific timeframe. The EGW_MAX_PER_ADDRESS setting specifies the maximum number of emails that will be accepted from an individual email address within the time period specified in the EGW_MAX_MSG_DURATION setting. This is used to identify and stop auto-responder email loops. For example, if this setting is set to 23 and 24 emails are received from the same address within EGW_MAX_MSG_DURATION hours, the 24th email from that address will be discarded and no response email will be sent, thereby breaking the email loop. Setting the value to zero will disable this loop detection. This setting is set to 23 by default. The EGW_MAX_MSG_DURATION setting specifies the number of hours to determine if an email loop is occurring. We recommend the duration not be less than 8 hours or more than 24 hours. The default value is 12 hours. By default, the system will only accept 23 messages from a given email address in a 12 hour period. If you use the default settings, the 24th and subsequent emails from that address will be discarded and no response email will be sent from the system. Important! If you use forms to submit information and create incidents within your Oracle B2C Service application, incidents created from the form are all associated to the same contact record. As a result, if the form is used more than 23 times in a 12 hour period (if using the default settings), then the 24th and higher submittals will be discarded and no response sent. Therefore, if you are using forms within your answers, you should set the EGW_MAX_PER_ADDRESS value to be 0 to disable the loop protection.
Note: These configuration settings are set at the per interface level. However, they function as the maximum per mailbox associated to the interface the configurations are set. To help illustrate the 'per mailbox' functionality: - If a contact is sending 25 emails to the same mailbox (mailbox_id 1) within 12 hours, only 23 incidents will be created and the last 2 messages will be discarded; - If a contact is sending 33 emails to 3 different mailboxes (10 emails to mailbox_id 1, 11 emails to mailbox_id 2 and 12 emails to mailbox_id 3) 33 incidents will be created and no email will be discarded.
See also Configurations EGW_MAX_PER_ADDRESS and EGW_MAX_MSG_DURATION explained for more information.
Add Email Address to Discard Addresses: To break the loop, you can temporarily add the offending email address to the discard addresses list for the mailbox. Leave the address in the discarded address list through at least one run of the techmail utility, which will break the loop. Then, you can determine whether the email address is for a valid contact and determine whether that address should be removed from the discard list so that that contact can submit email in the future. If not, you can go ahead and leave that email address in the discard addresses list.
IF Incident Source is Email and Incident.Subject matches regular expression Out of office|auto-reply|undeliverable THEN Do not create incident