MSGraph Mail Poller

Performance Optimization Tip: Reduce Graph API Payload When Generating EML Files

Context: When generating EML files without file attachments, we can avoid retrieving unnecessary attachment data from Microsoft Graph API.

Location: In the extractDataAndDocFromMimeContentProxied method, when processing the EML generation path that excludes file attachments.

Recommended Change:

Use selective field retrieval with .select("id"):

AttachmentCollectionPage attachments = mc.graphClient.users(mailbox)
    .messages(copyMsg.id)
    .attachments()
    .buildRequest(requestOptions)
    .select("id")
    .get();

Instead of retrieving all fields:

AttachmentCollectionPage attachments = mc.graphClient.users(mailbox)
    .messages(copyMsg.id)
    .attachments()
    .buildRequest(requestOptions)
    .get();

Benefits:

• Reduced network transfer: Avoids downloading large contentBytes from each attachment
• Faster API response: Graph API returns only attachment IDs instead of full attachment data
• Lower memory usage: Especially beneficial for messages with multiple large attachments
• Same functionality: Attachment IDs are sufficient for deletion operations

Performance Impact: For messages with large attachments (e.g., 5+ files totaling 50+ MB), this can reduce API response time by 50-70% during EML generation without attachments.

This optimization applies specifically when generating EML files where file attachments are excluded (isKeepFileAttachmentsInEml != INCLUDE).

Hope this helps optimize your Graph API integrations!

Best regards,
NLC

Is your DB in the right utf8 collation?

Bearer Token Not Being Passed in Proxied Requests to Microsoft Graph API

Issue Description:
When using the MS Graph Mail Poller plugin (version 4.3.2) with proxy authentication enabled (isConnectedViaProxy = true), requests to Microsoft Graph API fail with HTTP 401 Unauthorized errors. The Bearer access token is not being included in the API requests.

Root Cause:
In the MSGraphConnector.java file, the OkHttpClient (serviceHttpClient) is being built at line 73 BEFORE the TokenCredentialAuthProvider is created at line 97-99. This means the HTTP client is constructed without any mechanism to attach authentication tokens to outgoing requests. Even though the TokenCredentialAuthProvider is later passed to the GraphServiceClient builder, the underlying HTTP client was already finalized without token support, so it never adds the Bearer token to requests.

Suggested Fix:
The code in the isConnectedViaProxy block needs to be restructured:

1. Remove the early serviceHttpClient build (lines 67-73)
2. Create the TokenCredentialAuthProvider first (before building the HTTP client)
3. Use HttpClients.createDefault(tokenCredentialAuthProvider).newBuilder() to initialize the HTTP client builder - this ensures tokens are automatically included
4. Add proxy settings, timeouts, and proxy authenticator to the builder
5. Build the serviceHttpClient as the LAST step after all configuration is complete

The key is using HttpClients.createDefault(tokenCredentialAuthProvider) which creates an OkHttpClient.Builder that's pre-configured to inject Bearer tokens into all requests. The current code bypasses this by creating a plain OkHttpClient.Builder without the token provider.

Impact:
Without this fix, proxy-authenticated environments cannot retrieve emails. With the fix, Bearer tokens are properly included and authentication succeeds.

Hello Team,

The plugin seems to replace special characters with a question mark. Is this an expected behaviour? Thank you in advance.

Eg: Subject line - テスト日本ඞ﷽

Whats written to the DB - ??????????

• Updated DBHandler to fix SQLi vulnerabilities.

• Security Updates - High

• Conversation ID and Conversation Index are now saved from the inbound email to the database.

• Additional Note:
• Use the add-on database scripts from supplemental files while upgrading.
• This DB scripts are add on to the existing ones in the supplemental files and to be used only after upgrading to new version. If using old version existing DB scripts works, if using V4.3.0 and above use existing ones + add-on DB scripts.

• Upgraded angus dependencies for vulnerability fixes.

• Performance improvement for handling large sets of email attachments.

Could you share the Tomcat error stack trace?