Recipients list sepeated by comma. Should be semicolon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2017 01:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2017 01:14 AM
You might need to change the logic of the recipients. Suppose, you are sending an email a list of recipients/users on update of an incident. So rather than defining the recipients directly in notification, call a BR on update, call an event from that BR, define a string and add recipient emails:
var x= email1+';'+email2+';'+email3;
x=String(x);
Send x as parameter in the called event.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2017 01:23 AM
So the system cannot be setup to behave properly?
My Exchange supporter says that Exchange have behaved this way since 2005
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2017 01:46 AM
I am pretty sure there is a catch here. Even tough the recipients are comma separated, Exchange Server converts these commas into semi-colons. You can check if there is a rule written on exchange end that is not doing this conversion, or you can contact ServiceNow HI Support (if coding is not an option).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-10-2017 04:14 AM
It seems that my basic problem is not comma/semicolon, but that ServiceNow is set to use "SMTP Relay" instead of real SMTP. This apparently prevents our Exchange server to accept mails for groups. The problem is if I change the SMTP connection from "relay" to "login", our Exchange server accepts mail groups - but not individual mails! (????????????????)
I'm working on this now!