Microsoft Graph Support Now Available in stable

[Martin - Aqua Mail Support]

Hi all,

Two things:

1. Microsoft is retiring/blocking EWS for Microsoft 365 and requiring modern OAuth access through Microsoft Graph. Aqua Mail must use Graph to keep mail sync working securely. Admin approval is controlled by your company tenant, and Aqua Mail cannot bypass it.

2. At the moment we do not have a confirmed timeframe for shared mailbox support in the new Microsoft Graph implementation. We are aware of the issue, and it is something we want to add in the next update, but I don’t want to give you an unreliable date.

Main Microsoft 365 mailbox support is being maintained. The reason for the recent change is exactly because Microsoft is moving away from the older EWS method and toward Microsoft Graph. Aqua Mail’s new Microsoft 365 setup is intended to keep normal/licensed mailboxes working with Microsoft’s newer requirements.

For your shared mailboxes, converting them to normal licensed mailboxes may work, because they would then have their own Microsoft 365 login and could be added as separate main accounts in Aqua Mail. Your IT admin would need to confirm the licensing, permissions, and any effect on sending/receiving rules before changing them.

[Martin - Aqua Mail Support]

I'm running into a send failure on my Office 365 account since today's AquaMail update, which appears to coincide with the Microsoft Graph migration mentioned in your forum thread "Microsoft Graph Support Now Available in the Latest Aqua Mail Beta."



Device: Samsung Galaxy Z Fold 7 (Android)

AquaMail version/build: [please fill in from Settings > About AquaMail]

Account affected: Microsoft 365 Business Basic account on a custom domain (Exchange/O365 account type)



Error message on send:

"Error sending outgoing messages: Invalid server response: RequestBodyRead: Requested value 'plain' was not found."



Details:

- This started immediately after installing today's update.

- It only affects the O365/Exchange account. My other two IMAP/SMTP accounts on the same device send normally.

- I've already confirmed in Microsoft Entra ID that admin consent for AquaMail's Microsoft Graph permissions has been granted at the tenant level (17 Microsoft Graph delegated permissions showing under the Admin consent tab), so this doesn't appear to be a permissions/consent issue.

- Incoming mail sync appears unaffected; it's specifically outgoing/sending that fails.



Given the error text references a "plain" value not being found during request body parsing, this looks like it could be a content-type/message-format enum mismatch introduced in the new Graph-based send path.
Also contact pictures and calendar colors are not sinking correctly

Sorry for the inconvenience. We have identified the issue, and a fix is currently being tested for the next release.

In the meantime, please use the Rich Text Editor as a workaround until the update is available. Thank you for your patience, and apologies again for the trouble.

[Martin - Aqua Mail Support]

Regarding the Callendar issue:

We’re investigating this issue and believe we have an idea of where it may be coming from. However, we haven’t been able to reproduce it on our side yet.

At this point, it looks like the server may not be able to process all requested data before the connection times out.

Could you please confirm whether you have a large number of calendar events, especially recurring events or events with many attendees/attachments? This would help us narrow down the cause.

[phred]

AquaMail version/build: [please fill in from Settings > About AquaMail]

[JSSMarathon]

Thanks Martin — appreciate the update on the send fix and the Rich Text Editor workaround, I'll switch to that in the meantime.

One item I don't think got addressed yet: contact photos for my favorite/starred contacts aren't being retained since the update. They showed correctly before, and now they're missing or not displaying after syncing under the new Microsoft Graph setup.

Is this a known issue on your end, or would you like me to send a debug log to help track it down? Happy to provide whatever details are useful (account type is Microsoft 365 Business Basic, same account affected by the send bug).

[egal8888]

I just wanted to thank you for releasing 2.6.1-049

Shared mailboxes are now working as expected.
I did not expect such a fast fix for this.

Thanks again.

[Lippa]

I just wanted to thank you for releasing 2.6.1-049

Shared mailboxes are now working as expected.
I did not expect such a fast fix for this.

Thanks again.

Shared mailboxes working okay here also. But if i rename my main account it always asks me to re login and then renames it again. If fails to sync otherwise.

Any help here ones

[JSSMarathon]

AquaMail 2.6.1-049. Samsung Galaxy Z Fold 8 Ultra, Android 17, One UI. Microsoft 365 Business Basic account (Exchange/O365 type, custom domain).
Bug: Attachments disappear from message view after moving a message between folders, and never recover — even after force-closing/reopening the app or refreshing.
Root cause found in debug logs: After a folder move, AquaMail's internal attachment count correctly shows 1 (log: "MessagePartBag Message part count: 1"), confirming the file is still linked to the message and downloaded successfully. But the separate counter that controls what actually renders on screen stays at zero (log: "Left to load: state 0, total 0, 0 display, 0 inlines") — identical to a message with no attachment at all. The attachment exists in the data but the UI never builds a visible attachment row for it.
Steps to reproduce:
Receive or forward an email with an attachment into Inbox
Move the message to a different IMAP/Exchange folder
Open the message — attachment is missing from the display
Force-close app, reopen, view again — still missing
Impact: This is blocking normal use of the app for business email. I no longer trust AquaMail to show attachments correctly and have to verify every moved message in Outlook/webmail instead.
I don't have the earlier debug logs (deleted), but the above is a precise, repeatable description with the exact log lines that show the mismatch, if that's enough to go on.

[JSSMarathon]

Separate issue from my attachment post above — also from the same debug session (ticket #52935 was about push not working; not sure this fully resolved).
Log shows Microsoft rejecting AquaMail's push subscription request twice:
Graph subscription create failed: folderId=80 account=JSS - Exchange msg=ExtensionError: Operation: Create; Exception: [Status Code: 429; Reason: Too Many Requests]
This happened twice in one session. When this fails, does AquaMail fall back to polling instead of push? That would explain delayed mail delivery independent of the attachment bug. Is this a known rate-limit issue with the Graph subscription renewal logic, and is there a fix planned?

[JSSMarathon]

Has there been any progress on this I've stopped using aquamail and I've switched to Outlook I tried using aqua mail for a while but there's really no point if it's not working surprised there's no response from the aqua male team

[solstars]

V2.6.2 updated this morning.  New mail is still not working correctly.  It always sends from the first account instead of the selected account.  This has bitten me more than once, as you have to manually select the account to send from, which is very easy to forget.

[JSSMarathon]

And I tried adding my Office 365 account and again once I try and move a email with an attachment to another folder the attachment is gone or at least just shows up as a DOT bin file so nothing has changed on my end