Illegal email address in inbound emails

erlfos
Giga Expert

Hi

I am trying to set up event monitoring for HP iLO4. I tried SNMP, but it is so hard to map all the events and traps via the Event Rules due to how the HP iLO MIBs are structured. I would therefore like to integrate these events via email. There are so few events that it should not be an issue with volume. However, I have ran into another issue I need help to solve. The emails sent from the HP iLO interface to SNOW end up in the "Junk" table because of this error string: "Email set to ignored because of disallowed from address, email_address_filter_reason = Illegal address".

I think this is because the FROM address is based on the iLO hostname and contains a '.', these are the headers:

From:=?utf-8?q?iLO=20ILOCZ3641TXVD?=<ILOCZ3641TXVD.@ourdomain.com>
To:ourinstance@service-now.com

Is it possible to allow this address somehow? Emails like these worked fine with our previous event management system (Pagerduty).

10 REPLIES 10

Hi @erlfos ,

okay, that is strange. At the moment I cannot explain why your emails are moved to the junk folder.

Maybe someone else has an idea or you reach out for the ServiceNow support to clarify that issue.

I would be really interested in that answer 🙂

Kind regards
Maik

ikc_jc
Tera Contributor

We are experiencing a very similar issue and was not able to find a resolution.

Likewise, some of the inbound emails are classified as junk emails due to one of the following error messages:

  • Email set to ignored because of disallowed from address, email_address_filter_reason = Illegal address
  • Email set to ignored because of disallowed from address, email_address_filter_reason = Missing final '@domain'

It seems to be that these events started to occur after the Paris upgrade (could be Orlando because we skipped Orlando release). 

It would be great if anyone has a solution for this 🙂

Did you find any solution for this? I have emails coming with a phone number in the "from" field and servicenow ignore them.

Hi,

 

We ended up raising a HI case and they provided the following KB article

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0858378

 

Hope this helps

 

Cheers

Hi,

Did you find a solution?