Some types of emails not getting imported. Any idea why?
Suleyman_Ozden
Customer Advanced IT Monkey ✭✭✭
We have emails that our Exchange connector does not import to service manager.
1. Emails that are signed. We only get signed emails to the mailbox from one sender.
2. Mails from Sharepoint. For certain document libraries emaisl get automatically sent but these mails are not imported. Kind of strange Service Manager is not importing mails from another MS product!
Anyone seen issues with certain types of emails not getting imported?
Best Regards
Suleyman
0
Best Answers
-
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
Hi @Suleyman_Ozden
The signed e-mails may not be being encrypted before they are processed or it may be some security restriction on them. I've not seen this one in the past.
As for the e-mail coming from SharePoint, the Exchange connector will process e-mails as long as the sending user is identified as having a valid user within SCSM. If the SharePoint server or a service account running SharePoint is the sending address it may not have a User CI within SCSM to map the e-mail to.
While you can add the SharePoint service account to SCSM, I would not recommend it as this clutters up your SCSM User CI entries.
Hope this answers your question5 -
Brian_Wiest
Customer Super IT Monkey ✭✭✭✭✭
This is an Microsoft Issue and I have seen it on a number of Connector services. Outside of Exchange connectors cannot process anything but messages. So special types in the inbox cannot be processed.
I have had to create special rules on my workflow mail boxes to handle this issues.
The list as I know it.
Signed Email
Out of office auto replies
Send Receipts
Read Receipts
SharePoint Alerts
Calendar Invites
6 -
Brian_Wiest
Customer Super IT Monkey ✭✭✭✭✭
Rule
Inbound = Type Signed
Foward email as attachment to =(Same mailbox)
Thus the message becomes a standard message with the Signed message as an attachment.
For SharePoint I use SCORCH to monitor the SharePoint listes.
The autoplies have rules to just delete.6
Answers
The signed e-mails may not be being encrypted before they are processed or it may be some security restriction on them. I've not seen this one in the past.
As for the e-mail coming from SharePoint, the Exchange connector will process e-mails as long as the sending user is identified as having a valid user within SCSM. If the SharePoint server or a service account running SharePoint is the sending address it may not have a User CI within SCSM to map the e-mail to.
While you can add the SharePoint service account to SCSM, I would not recommend it as this clutters up your SCSM User CI entries.
Hope this answers your question
I have had to create special rules on my workflow mail boxes to handle this issues.
The list as I know it.
Signed Email
Out of office auto replies
Send Receipts
Read Receipts
SharePoint Alerts
Calendar Invites
Hi Brett
For 1. the sender is external and does not have a user CI in the system. I thought everyone could send an email and get an incident created?
For 2. the sender address does have a CI in SCSM.
Hi Brian
Great info. What kind of rules did you end up creating? I am especially interested in the SharePoint alerts and the signed emails.
Inbound = Type Signed
Foward email as attachment to =(Same mailbox)
Thus the message becomes a standard message with the Signed message as an attachment.
For SharePoint I use SCORCH to monitor the SharePoint listes.
The autoplies have rules to just delete.
Very clever