Email spam scoring and filtering (instance security hardening)
Install the Email Filter (com.glide.email_filter) plugin to install email filtering within the instance. This filtering identifies existing headers, which enables you to decide what to do with the email based on the associated header.
Note:
If an instance uses a private email server, this topic is not
applicable. For more information, see Email Spam Scoring and Filtering.
Prerequisites
Before setting this property:
- Set the glide.email.read.active property to true. To learn more, see Enable using your own POP3 server.
- This filter overrides the glide.pop3.ignore_headers property. To learn more, see Available system properties.
More information
| Attribute | Description |
|---|---|
| Plugin Name | com.glide.email_filter |
| Configuration type | System Definition > Plugins |
| Configure in Instance Security Center | Yes |
| Purpose | To enforce filtering to avoid spamming of emails. |
| Recommended value | Active |
| Functional Impact | Email is never filtered, blocked, or quarantined from the instance as part of spam scoring. It is only scored and then sent on to the instance. All filtering is done within the instance with the Email Filters plugin. |
| Security risk | (Medium) Email filters enable administrators to use a condition builder or conditional script to specify when to ignore malicious incoming emails from known/unknown sender. |
| References |
https://support.servicenow.com/kb_view.do?sysparm_article=KB0549426 |
To learn more about activating a plugin, see Activate a plugin.