What can be done to stop SPAM email from becoming incidents?
Mailboxes, SPAM Filtering, Business Rules, All versions
Generally, bulk mail messages (spam) are automatically removed by the techmail utility, which checks to see if the originating mail server is the type commonly used for sending out mass mailings. The odds are good that many messages of this type are already being removed before they come into your Oracle Service Cloud application.
External Spam Filtering
The best way to avoid receiving spam email is to use a dedicated spam filtering tool.
Barracuda spam filtering is provided for mailboxes that are hosted by Oracle Service Cloud. You can configure spam filtering for each of your hosted mailboxes. For more information, refer to Answer ID 2345: Barracuda Spam filters on hosted Service mailboxes.
If you are using a mailbox that is not hosted by Oracle Service Cloud, it is strongly recommended that you use an external spam filtering utility. This will not only reduce the amount of unwanted email that you will receive, but also the chance that a mal-formatted spam message will disrupt the processing of valid email.
Discard Fields for Mailboxes
Within your Oracle Service Cloud application, each mailbox has discard fields which allow you to filter email based on content.
You can add specific email addresses to your list of Discard Addresses. Incoming email from addresses included in the Discard Addresses field are deleted before they become incidents and before a contact record is created. Consistently adding offending email addresses can prevent repetitive abuses by an individual.
Note: The list of discard addresses is separated by commas without spaces.
Similarly, you can update the Discard Subject or Discard Body field of your mailbox configuration with the phrase you want to match. Enter any text found in an email subject line that identifies an email as one to be discarded. Each entry should be on a separate line. For example:
Note: Emails are discarded based on whether the content matches any of the text strings entered and function similar to regular expressions in business rules. That is, if you include the entry "hat" as criteria to discard the email, emails will be discarded if they include words that have "hat" in them, including, "chat", "what", "hatch" and so on. For this reason, it is best to include longer words or phrases when adding content to these discard fields.
To modify any of the discard fields, use the steps below:
- In May 2010 and later: Go to Configuration > Site Configuration > Mailboxes
- In May 2010 and earlier: From the Service Configuration Items, select Communication Configuration > Service Mailboxes.
- In the left-hand frame, right-click on the mailbox name and select Edit.
- In the right-hand frame, click the Incoming Email tab.
- With the Filter menu set to Discard Addresses or Discard Subject and add content to the field as appropriate.
- Click Update.
Configure a Rule to Manage Emails
If spam and content filtering is not enough to block all unwanted messages, you can set up a rule within Oracle Service Cloud to look for a specific keyword(s) in the email and either:
- NOT create an incident if those words are included in the message, or
- create an incident but notify or assign it to someone who can review it for this type of content.
Important! Using rules in this manner is not foolproof -- messages may not match the rule specified, and there is a chance that the rule may act upon messages which contain the keyword(s) but are not actually spam.
The most common method for setting up this type of rule is to use regular expressions and the pipe ( | ) feature. The pipe is used to specify a series of words or phrases that you are interested in matching. The pipe acts as an OR operator between each item separated by the pipe character. For example, to set up a condition that matches the rule if the subject of an email contains "cat" or "dog", you can set up the criteria in the "if" section of the rule as listed below:
Incident.Summary matches regular expression cat|dog
You can then add additional criteria or specify actions to complete the configuration of your rule.
Once your rule is configured, be sure to test the rule by submitting test incidents to your site. Submit several incidents that will match the rule to verify that it will match the incidents you want it to. Also submit at least one incident that should not match to verify that it will not affect incidents that it shouldn't.