Question 4

Explanation

Three stages of Jira Cloud built-in processor:

• Email puller fetches emails from the service project’s associated inbox.

• Email processor filters pulled emails to remove auto-replies and spam.

• Database cleaner deletes old emails from the database.

Email puller

The puller fetches unread emails from the associated inbox every minute. It then copies them to the email database. Emails with a total size of more than 25MB (including attachments) are not fetched, and will remain unread in the mailbox or bounce back to the sender depending on whether they were sent to a custom or Atlassian-provided email channel. Emails received before the accounts are connected to the system are not included.

Email processor

The processor filters non-requests from the pulled emails. To do this, it filters emails based on the content of the auto-generated headers:

• Auto-replies filter out emails if the auto-submitted headers contain the keywords auto-generated, auto-replied, or auto-notified.

• Bulk mail filters out emails that the mail server marks as spam.

• Delivery status notifications filter out emails if the multipart/report header contains report-type-delivery-status, or if the return-path header has a null email address.

• Jira mail filters out Jira emails that your site sends by checking if they have X-JIRA-FingerPrint in the header.

Database cleaner

By default, the database cleaner purges all emails in the database that are older than 45 days. You can change the purge to a range of intervals from 14 days to 180 days on the Global Mail settings page.

There are no Email fetcher and Email analyzer in Jira Cloud. These are incorrect.