Filtering

Decide which mail is unwanted

Filtering incoming messages is important to avoid unwelcome use cases, like spamming from certain addresses. Email This Issue provides you with options to cover some frequent needs.

Filters are used during the mail fetching phase. If a mail is filtered out by these filters, it won't be queued for processing.

Note: From a higher-level perspective, filters can be categorized as follows:

• Filters that work in a global scope (e.g. sender address filters)

• Filters, whose scope is restricted to a given mail handler

In this document, you can read about mail handler-related filters.

In order to fine-tune filtering behavior, two categories of filters come into action:

• Accept (or pass-through) filters to restrict or customize which messages should specifically arrive at the mail handler’s processing phase (but not others).

• Reject filters to control which messages should be filtered out for any case and not arrive to the mail handler’s processing phase.

Filters can be configured on the Filter emails tab:

Filter emails tab

Accept filters

Accept email can be used to filter messages in a mailbox with multiple email addresses (like mail aliases).

The following options are available:

Accept email filter options

• If Accept email is set to for any recipients (default setting), all messages will be passed through, regardless of the recipient addresses.

• If Accept email is set to if any recipient equals to any of the following addresses then email will be processed only if the To/CC/BCC address of the email equals to any of the specified email addresses. For example, if you have a mailbox [e-mail] with aliases [e-mail] and [e-mail] and you want to process only emails sent to example.net or example.org (not example.com), then add two lines in the appearing text area: [e-mail] [e-mail]
• If Accept email is set to if any recipient matches any of the following regular expressions then email will be processed only if To/CC/BCC address matches with any of the specified regular expressions. For example, if you have a mailbox with addresses [e-mail], [e-mail], [e-mail], [e-mail] and want to process emails that are sent to addresses starting with support, then add this line in the appearing text area.

support(*.)@example\.com

Note: The dot is escaped before .com.

Reject filters

These are classical filters. If any of the activated filter conditions prove to be true, the incoming message will be completely ignored from further processing:

• Filter out auto-reply emails: If this filter is enabled, all emails with the Auto-Submitted header with a value other than no are considered auto-reply and will be filtered out.

• Filter out bulk emails: It checks and filters out emails in which the Precedence header with the value bulk is set.

• Filter out delivery status notifications: This filter checks if the content type is multipart/report and contains report-type=delivery:status , and filters out emails where it does.

• Filter out emails sent from Jira: This feature filters out emails sent from a Jira or Email This Issue Cloud instance. It checks the presence of X-JIRA-Fingerprint and X-JETI-Fingerprint headers and filters the email if either is present.

• Filter out emails sent by unknown senders: This filter checks if the sender has a user or customer account in Jira. The App searches by the sender's email address.

• Filter out email by content: This filter allows you to filter out emails with specified email content by matching /not matching a regular expression. You can select from the following email sources:

  • Body

  • Subject

  • Header

  • To address

  • Cc address

  • To/Cc address

  • From address

  • From name