Original Message:
Sent: Wed March 25, 2026 04:28 PM
From: Damian Parrinello
Subject: Datacap O365 Mailbox Scanning Time Outs
Thanks, I will have them check that. Back when we switched over to O365, I gave our Exchange team the Datacap connection/logon options we had and they told us to use the Client Secret login, not Graph. I can try testing that, if they can give me that option.
Thanks,
Damian
------------------------------
Damian Parrinello
Original Message:
Sent: Wed March 25, 2026 04:22 PM
From: Duke Lam
Subject: Datacap O365 Mailbox Scanning Time Outs
Let us know what you find. I used to be able to use client secret but switched over OAuthGraph. Maybe it's the 50 mailbox idle session Check your exchange admin. I found this setting. Maybe one of your 50 mailbox has this idle session enabled.
------------------------------
Duke Lam
Original Message:
Sent: Wed March 25, 2026 04:01 PM
From: Damian Parrinello
Subject: Datacap O365 Mailbox Scanning Time Outs
Thanks for the response. We have been running ingestions for our production mailboxes, since Datacap since 9.1.3, for quite a while. I don't know why we would have issues, now. Unfortunately, I cannot recreate these errors. They are random and don't affect any one mailbox, in particular. Client secret has been working fine. I'll continue to search for solutions to these random time-outs.
Thanks,
Damian
------------------------------
Damian Parrinello
Original Message:
Sent: Wed March 25, 2026 03:36 PM
From: Duke Lam
Subject: Datacap O365 Mailbox Scanning Time Outs
Hi Damian,
I don't think it can handle handle 50 mailbox. Have you try with just one mailbox to see if the bind is still failing?
I also think client secret is no longer working or supported.
Please try OAuth_Graph.
------------------------------
Duke Lam
Original Message:
Sent: Tue March 24, 2026 08:54 AM
From: Damian Parrinello
Subject: Datacap O365 Mailbox Scanning Time Outs
Hello,
I'm trying to track down an issue with our O365 Exchange connections and email scanning/processing. We are currently running Datacap 9.1.9 and have roughly 50 production mailboxes to monitor. We are randomly getting time-out aborts during this process; this was not an issue until switching to O365. I have asked our Messaging Team (who handle Exchange/Email in our company) but they haven't been able to provide any answers/help.
The time-out in question seems to be happening at around 100 seconds. In looking at the ewsmail actions, there is an ex_HTTP_timeout that defaults to 100 seconds. However, I have added this action and set this to 300 seconds, for all mailbox rulesets but there has been no change in the time-out aborts. I have tried many ewsmail action configurations but nothing seems to affect this time out. Again, this is random, as the mailbox processing works most of the time. Unfortunately, the number of aborts per day is becoming a maintenance issue. Below is a screenshot of an example of one of our mailbox-scanning setups (these are pretty much the same across all Datacap apps/mailbox processing rulesets) and some RRS log snippets. Has anyone come across this issue or have any suggestions?
EXMAPLE 1:
08:15:52.5 Login to Office 365 with OAuth
08:15:52.5 Create EWS
08:15:52.5 EML 1
08:17:32.344 Failed to bind Exchange Web Service with supplied credentials. Error message follows.
08:17:32.344 The request failed. The operation has timed out
EXAMPLE2:
09:08:19.623 Login to Office 365 with OAuth
09:08:19.623 Create EWS
09:08:19.623 EML 1
09:08:20.100 Connected to Exchange Web Service
09:08:20.103 Action esec='0.50000'
09:08:20.103 hr_locale = en-US
09:08:20.104 Maximum Docs (emails): 1
09:08:20.734 Total pending items: 4
09:08:21.661 Processing item: Microsoft.Exchange.WebServices.Data.EmailMessage
09:08:21.661 Item ID: {XXXXXXX - removed for security reasons}
09:08:21.661 Msg ID: {XXXXXXX - removed for security reasons}
09:08:21.661 Sender: {XXXXXXX - removed for security reasons}
09:08:21.661 Attachments: 2
09:08:21.661 IsMessageIngestable email attachment count2
09:08:21.661 No extensions specified
09:08:21.661 j : 2 bNoAttachments: False
09:08:23.27 Bind success
09:08:23.27 ProcessInboxItem, Calling AddDoc()
09:08:23.27 AddDoc (process)
09:08:23.29 AddDoc, create document with unique ID in the runtime DCO batch (docID): LIS Email 20260317_000196.1
09:08:23.29 AddDoc (nDocsGotten): 0
09:08:23.29 Email docid LIS Email 20260317_000196.1
09:08:23.38 AddDoc, Document created OK in setup DCO: LIS Email 20260317_000196.1
09:08:23.38 AddDoc, add email parts to DCO: LIS Email 20260317_000196.1
09:08:23.38 To: {XXXXXXX - removed for security reasons}
09:08:23.38 RecipientAddresses: {XXXXXXX - removed for security reasons}
09:08:23.38 Body added
09:08:23.38 ProcessInboxItem, Calling AddDoc() done
09:08:23.38 IMAGEFILE \\XXXXXXX - removed\Datacap\LIS\batches\LIS Email 20260317_000196\TM000001.eml
09:08:23.40 Added .eml page P1.0
09:08:23.46 Write file: \\XXXXXXX - removed\Datacap\LIS\batches\LIS Email 20260317_000196\TM000001.eml len 85833
09:08:23.61 Moving message to folder: Done
09:08:23.61 Searching for folder Done
09:08:23.977 Folder found: Done
09:08:23.977 Searching for folder Done
09:08:25.221 Folder found: Done
09:10:08.967 Failed to move email to Done
09:10:08.967 The request failed. The operation has timed out
------------------------------
Damian Parrinello
------------------------------