How to bypass email inbound default filters like ignore sender and ignore header
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2020 05:13 AM
We have inbound setup in our customer instance, where in it process the incoming email if it has the specific subject.
It works fine for some users but not for everyone. When an email is received, it's not getting processed. Type is being set to "received-ignored" and the error string is "Ignoring inbound email with subject 'abc' or MAILER-DAEMON@somexyz.com. Reason(s): ignored sender"
Just wanted to know how this is not getting processed even though user is present (email ID is different on user profile)
Our requirement is allowing the emails to be send via the email inbound actions, even if they are not whitelisted, if possible. It should only evaluate if the subject matches to what we define, but it shouldn’t evaluate if the user exists in ServiceNow or if the email is generated by other instance of ServiceNow.
Is there any way to bypass the email filters to process an incoming email?
Any help on this much appreciated.
- Labels:
-
Notifications

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2020 05:31 AM
Hi,
There are some rules in servicenow which recognize email as spam and put it to junk. Because OOB service Now has defined some rules on it and if you want you can modify it but it will create unnecessary noise for you.
You can see below: Basically you can then see conditions and edit it as per need. But this is really important to avoid spam and security.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2020 04:16 AM
Hi Ashutosh, Thank you for your reply. Could you please elaborate on why you think it will create unnecessary noise if OOB email filters are modified..?
Another question : ServiceNow ignores email sent by another ServiceNow instance. again this is because of the ignore header email filter (only when an incoming email header contains 'X-Service-now-Generated = true')
I see one Hi article about this, ServiceNow suggest Web service Integration / Email based integration.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0551482
Is there any other way to process the emails coming from another SN instance? like setting up an user account or something like that
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2020 07:06 AM
Hi Bhavani,
sharing links for help; I would encourage to go through
https://hi.service-now.com/kb_view.do?sysparm_article=KB0538110
https://hi.service-now.com/kb_view.do?sysparm_article=KB0813088
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2020 04:21 AM
Hi Ankur,
I have gone through these links and understood that Email filters can be customized. I would like to know what are the consequences if any one of the OOB email filter is modified.
Another question : ServiceNow ignores email sent by another ServiceNow instance. again this is because of the ignore header email filter (only when an incoming email header contains 'X-Service-now-Generated = true')
I see one Hi article about this, ServiceNow suggest Web service Integration / Email based integration.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0551482
Is there any other way to process the emails coming from another SN instance? like setting up an user account or something like that