Users want to create a case by sending an email to a specified email account. An issue with the email account configured for email instantiation occurs and case creation fails.

The email account that you configured for case instantiation is currently in use by another case type.

1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
2. On the Settings tab, click Email instantiation.
3. Clear the Enable email listener check box.
4. Find and manually delete the set of standard rules that your application created when you enabled email instantiation for your case type.
   For a list of these rules, see Standard rules used by email instantiation.

   Caution: Do not delete the email account itself because another case type might rely on it.
5. In the case type rule form header, click Save, and then click ActionsRefresh.
   Result: You disassociated the email account from your case type.
6. Create a new email account exclusively for your case type.
   For more information, see Creating an email account.
7. Enable email instantiation for your case type by using your new email account.
   For more information, see Enabling creation by email of top-level cases.

The email account that you configured for email instantiation has issues when sending or receiving emails.

1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
2. On the Settings tab, click Email instantiation.
3. Below the Email address field, click the email address that you associated with the case type, as shown in the following figure:

   

   

4. On the Email account tab of the email account rule form, test connectivity:
   • If the email account cannot send emails, in the Sender section, click Test connectivity.
   • If the email account cannot receive emails, in the Receiver section, click Test connectivity.
5. In the Test Connectivity window, review the test results.
6. Optional: To obtain more information for debugging, inspect the log files:
   1. In the header of Dev Studio, click ConfigureSystemOperationsLogs.
   2. On the Logs tab, in the Log utilities section, click Log files.
   3. In the Log File Download window, examine the logs.
      For more information, see Viewing logs.

Incoming email messages include redundant HTML tags that cause case creation by email to fail.

1. In the navigation pane of Dev Studio, click Records.
2. Expand the Technical category and click Activity.
3. In the list of activity instances, open the pyTreatIncomingText activity.
4. In the rule form header, click Save as.
5. In the Context section, in the Apply to field, select a class that includes the case type that you configured for email instantiation.
6. Click Create and open.
7. In row 1. of the activity that includes a Java method, click Expand to see method parameters.
8. In the Java Source text box, edit the Java script to exclude HTML tags from the email text:
   • To remove tags related to script and script elements, include the doc.select("script").remove(); line in the script.
   • To remove tags related to styling, include the doc.select("style").remove(); line in the script.
   • To remove tags related to formatting, include the doc.select("form").remove(); line in the script.
   • To remove line breaks, include the doc.select("br").remove(); line in the script.
   • To remove metadata tags, include the doc.select("meta").remove(); line in the script.
   For example: The following figure shows a Java script in the pyTreatIncomingText activity before and after removing redundant tags from the email text:

   

   

9. In the activity header, click Save.

The email provider that you included in the email account configuration flagged your email account as suspicious.

1. Access your email account by using a web browser or supported client application.
2. Log in by entering your user name and password.
3. Follow any additional steps from your email provider to successfully access the account.
   For example: The email provider might require a phone number to send you a verification code.

Email listener does not respond because the email messages are marked as read.

• Do not open and read email messages because email listeners respond only to unread messages. Notify your development team of this restriction.