Inbound Email Ignored Due to Auto-Generated Headers & Notification Suppression Issue

[Yougander patel]

Issue: Inbound Email Ignored Due to Auto-Generated Headers & Notification Suppression

Hi Team,

I’m facing an issue with inbound email processing and notification behavior in ServiceNow. Below are the details:

---

Scenario

• A client is sending emails from their ServiceNow instance.
• Subject format: LOIT-POIT56787
• Emails are sent to my instance: jik@servicenow.com
• These emails are auto-generated from their system.

---

Problem 1: Inbound Email Ignored

• The emails are not creating incidents.
• From email logs, I see:

“Skipping script ‘Unsubscribe from Notification’, ignored by filter”
“Ignoring inbound email… matched user or email condition(s): ignored headers”
“The inbound email processing was bypassed due to its exclusion by the system filter.”

• Identified headers causing the issue:

  Precedence: bulk
  Auto-Submitted: auto-generated
  X-ServiceNow-Generated: true

• If I remove these headers and reprocess, the incident gets created successfully.

---

Workaround Implemented

• Created a Power Automate flow:
  1. Email received at servicedesk mailbox
  2. Forwarded to a shared mailbox
  3. Headers effectively stripped
  4. Email sent to ServiceNow again
• Result: Incident is created successfully

---

Problem 2: Notification Issue

• After incident creation:
  • I created a custom notification to send updates back to the client
  • Tried using the original subject (LOIT number) in the notification
• Issue:
  • Notification is not sent when using original subject
  • If subject is changed → notification is sent
  • Indicates system suppresses notification based on subject/header logic

---

Additional Context

• The sender/user is not present in AD
• Likely treated as a system-generated or filtered sender

---

Questions

1. Is there a recommended way to allow auto-generated emails (with these headers) without bypassing filters?
2. Can we override or ignore these headers safely within ServiceNow?
3. Why are notifications suppressed when using the original subject?
4. Is this behavior tied to:
   • Email filters?
   • Notification suppression rules?
   • Duplicate detection?

---

Goal

• Allow inbound emails from external ServiceNow systems without workaround flows
• Ensure notifications are sent with original subject intact

---

Any guidance or best practices would be really helpful.

Thanks in advance!

[Mark Manders]

That doesn't make sense. A notification that is triggered will never have a 'received' type. Are you sure you are looking at the correct mailbox?

[Yougander patel]

@Mark Manders  can you please have a look on my update ?

[Yougander patel]

@Mark Manders 

Thanks, it’s working now.

However, I’m facing one issue. When a notification is sent using the original subject from the user’s email, it is not being delivered properly.

The notification subject is:
${number} has been created | ${short_description}
The original inbound email subject is:
[EXTERNAL] LOIT-POIT56787 - Requires your input - System not receiving LIOT ASUOps

I tried using different subject formats like:

[EXTERNAL] LOIT-POIT56787 - Requires your input
${number} | Re: ${short_description}
Incident ${number} created - ${short_description}
${number} created | Original: ${short_description}
What I understood (step by step):
When the same subject (or very similar subject) is used,
→ the system treats the email as a reply
→ so the notification is not sent properly
When a different subject is used,
→ the system treats it as a new email
→ and the notification works fine