How to have multiple SMTP servers in ServiceNow? (Workaround)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2019 06:14 AM
- Labels:
-
Notifications
- 6,177 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 05:46 PM
Thanks for the reply, the Reply-To field only gets a response from the recipient when the email was delivered in first place and then they reply back to that email.
In our case, if we change the from address and email is wrong, we don't seem to get back the failed email notification in ServiceNow email logs. I think the failed email goes back to the from address and this only works if we use the default email for ServiceNow instance.
Still thinking of a way to get those failed emails back in ServiceNow if we change the from email.
This is how it looks like in ServiceNow logs if we send it from ServiceNow default email to an invalid email:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 11:34 PM
Well I've never tried spoofing a non-existent mailbox TBH. The way I set it up usually is that there is a dedicated mailbox created in the client's domain. Then the client adds ServiceNow SPF records/IPs to whitelist to allow spoofing of that mailbox.
Then this mailbox is set in both the FROM and Reply-To headers. A redirect is set up on that mailbox to route any incoming emails back to ServiceNow.
I'm pretty sure that way my clients were getting all sorts of out-of-office or mailred-daemon replies back to ServiceNow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2021 04:26 PM
Thanks, this is working with a personal mail, but mailred-daemon is not getting back on a corporate mailbox. Do we need to contact ServiceNow for SPF records/IPs to be whitelisted to allow spoofing of that mailbox?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2021 11:29 PM
You will find this information in your HI Account. But generally, for SPF records:
a.spf.service-now.com - Canada
c.spf.service-now.com – US & Europe
d.spf.service-now.com – other data centers
The alternative is to whitelist individual IPs (note those can change without a warning though, SPF is more "general" thus stable but some companies have issues with this kind of whitelisting).
To get the IPs either go to HI or run the nslookup command for the specific SPF, e.g.
nslookup c.spf.service-now.com.
This will give you several different IPs, you have to whitelist them all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2023 06:48 PM
For anyone who might come upon this thread in the future, I had a similar requirement where mail had to be sent from two different domains that did not share the same smtp server. I ended up using solution #1 above by setting up Amazon SES. This is, of course, a paid service, however mail is delivered cleanly and without spoofing or any shenanigans.