Demystifying Inbound Email Action Processing

-






Inbound action is all about how servicenow responds when an email is received by the system. Based on the logic inbuilt in the system, email received is categorized as new/forward/reply, and then continues the processing.

 

What triggers inbound and what’s the frequency

In every two minutes servicenow runs a schedule job named Email Reader. It connects to the mail server using the account specified in Email Properties. The Email Reader downloads any incoming message that is waiting on the mail server and creates email.read events. After the instance processes the events, the inbound actions run. Based on the logic inbuilt, it identifies whether email received is new/forward/reply.


              

Identification of the Sender of the email

Servicenow identifies the user who sent the email based on the email id of the sender. As soon as servicenow receives the email, it matches the sender’s email id with all the user’s email id in the user table. if there is any match found then sender is identified with that matched user id. In case if there is no match found then system considers the sender of the email as a guest user (Provided “Automatically create users for incoming emails from trusted domain” property of email is unchecked else it will create a new user and will refer to that user as a sender of the email).

Processing of inbound email

Once email is received by the platform, first it is checked if email is worth processing based on the below conditions:

1.      Does subject line start with text like “out of office autoreply”?

2.      Does sender’s email id match email id of any existing user in user table and user is logged out?

If any of the above two condition evaluates to true, then Mailbox value of the email is set to Skipped and processing of the inbound will stop. If both above condition evaluates to false, then processing of inbound will move further and now it will try to categorize it as one of new/forward/reply. Below is the Sequence of categorization:

1.      Forwarded email – First inbound email is tried to categorize as forwarded email. If it fails it will move to the other categorization

2.      Reply email – If inbound fails to categorize email as forward, it tries to categorize it as reply.

3.      New email – If inbound email fails to categorize as forwarded or reply then it is considered as a new email.

This sequence is fixed and cannot be changed. Let’s discuss each categorization one by one.

 

Logic to identify email as Forward:

If the subject line of the email is prefixed with recognized/defined forward prefix and string From appear anywhere in the body of the email. In platform, forward prefix is defined in “Identify email as a reply by these subject prefixes” property of the email properties as shown in the below screenshot:



 

Logic to identify email as Reply:

If any of the below condition evaluates to true, then email is marked as reply:

1.      Does email subject prefixed with Re and contains and contains system recognized record number like INC0010061?

2.      Does email body contains a valid watermark like Ref:MSG0140490_lRhI4zra325ws7oc8NwO

3.      Does email body contains In-Reply-To header, having value same as Message Id field of any other email table record as shown in below screen shot? (We will discuss this in detail and will deep dive using Use-Case in a separate blog)





Logic to identify email as New:

When system fails to categorize received email as forward or reply, it is identified as New

 

Flow of determining the type of incoming email



Image source : Servicenow Doc (https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/administer/notification/concept/c_InboundEmailActions.html)

 

Below are the email properties where prefix identifier for reply and forward are defined


 


 

 

 

 

 

 

Comments

Post a Comment

Popular posts from this blog

How to create custom probe and sensor.

-
Image
Creating custom probe and sensor. Before starting this I assume you already know what is probe and sensor and what does it do.If you are not aware of probe and sensor then please go through this link first  Probes and Sensor. Here we will try implementing a very small and basic requirement. Once you understand how it works you can implement any complex requirement also. So here we will try to fetch the BIOS information of a windows system and will populate this result into the BIOS detail field ( which is a custom field that I have created ) of CI table . Let's start with probe first :- To create a probe follow the below steps :- 1. Under Discovery definition click on probes module. 2. Give a meaningful name to the probe. Ex. Windows-BIOS version . 3. The value in the ECC queue topic field appears in the ECC queue output record's "topic" field when this probe is launched.Since its a DOS command write Command in the field. Please
Read more

Discovery Probes and Sensors

-
Image
Discovery Probes and Sensors Introduction Discovery is a module that servicenow provides in order to maintain CI's data that are present in the network of an organization. It is an automated process which means you just need to configure this and it will work on it's own i.e mannual intervention is not required ( given nothing is going wrong and you have configured it as expected) . The basic functionality of discovery is to knock the door of each and every device that are present in your network. Then classify which kind of device it is ex. computer, server etc. Then gathers the detailed information of the device like Serial number, Version and so on and populates all these data into the cmdb_ci table.  Now the one who is responsible for knocking the doors and gathering data is what is called Probe and the one who is responsible for analyzing these data and populating cmdb_ci table is what is called Sensor.  The one who does the coordination between the servicenow and
Read more

The Year changer - YYYY

-
Image
                                               The year changer YYYY Did you know that the year format yyyy and YYYY are not same? Although round the year you would find both format working for you in the same way but, when the year is to end and there is a transition of the year to happen, at that time you may get the unexpected result if you do not choose the right format. So, what's the difference ? Let's discuss this. yyyy - This format represents the calender year. Now what does it mean? It means this format evaluates the year part as the year in which day and month of the date lies. You would say it's a waste of time, I already know this, what's new. I agree, till this point nothing new but, let's see the other format YYYY -  This format represents the 'year of the week'  or to simplify, year of the last day of the week. Wait, Does it mean any thing? Yes, it does. To understand the meaning of it, let's take an example :  var Date = new GlideDate(
Read more