AquaMail Forum
English - Android => Development builds => Topic started by: Martin - Aqua Mail Support on June 26, 2026, 12:17:19 pm
-
Hello everyone,
With the latest Aqua Mail beta update, we have implemented the long-awaited Microsoft Graph support for Microsoft business accounts.
To continue using your Microsoft 365 / Office 365 business account in Aqua Mail, you will need to remove the account from Aqua Mail and add it again.
More info here: https://aquamail.freshdesk.com/a/solutions/articles/77000596845
-
But we will loose ALL the personalization/folder/settings (for AquaMail) for that account - correct?
-
Is there any way to get past this page other than contacting our institional IT department and trying to get their permission to keep using Aquamail?
-
Hello Martin,
I updated the new Aquamail version but I have found problems. After I deleted my Office365 account and I added again the same Office365 account It seems that it was working fine, but, after some hours the account asked me again for the credentials and for giving access to contacts, calendar, etc. I gave it but for some reason, it didn't work.
Now, I am trying again, I hope it will work, but there is some things to fix. I am adding 2 examples, to show the outlook view and the Aquamail view. Aquamail is showing for some emails, many times the email address of the contacts used in the mail.
-
I noticed too that the calendar is syncing some events with error.
You will see that there is a repetitive event "Visita al Santísimo", it is shown in Saturday instead of Sunday.
Can I download the previous version? I hope it will be available.
Regards
-
Hi everyone,
Thank you for the feedback!
But we will loose ALL the personalization/folder/settings (for AquaMail) for that account - correct?
Yes you will.
Is there any way to get past this page other than contacting our institional IT department and trying to get their permission to keep using Aquamail?
Not at the moment, but we will look for a possible solution.
Hello Martin,
I updated the new Aquamail version but I have found problems. After I deleted my Office365 account and I added again the same Office365 account It seems that it was working fine, but, after some hours the account asked me again for the credentials and for giving access to contacts, calendar, etc. I gave it but for some reason, it didn't work.
Now, I am trying again, I hope it will work, but there is some things to fix. I am adding 2 examples, to show the outlook view and the Aquamail view. Aquamail is showing for some emails, many times the email address of the contacts used in the mail.
We are currently investigating all reported problems, including this one. I will keep you updated on the progress.
I noticed too that the calendar is syncing some events with error.
You will see that there is a repetitive event "Visita al Santísimo", it is shown in Saturday instead of Sunday.
Can I download the previous version? I hope it will be available.
Regards
Please send us some details at support@aqua-mail.com
To use the stable version, you will need to leave the beta program from Google Play > Aqua Mail, then reinstall Aqua Mail.
-
Is there any way to get past this page other than contacting our institional IT department and trying to get their permission to keep using Aquamail?
Probably not. And if there is and your IT department catches you, there's a good chance you'll be terminated. If you're not allowed to use third-party apps by your company, then you're not allowed to use third-party apps.
-
I'm facing the same admin approval issue now. Were you using Azure AD Graph previously? I have to explain the change to our MS admins.
-
I'm facing the same admin approval issue now. Were you using Azure AD Graph previously? I have to explain the change to our MS admins.
No, this change is not about Azure AD Graph. Azure AD Graph is a directory API and is being retired by Microsoft.
Aqua Mail has moved Microsoft 365 accounts to Microsoft Graph for mailbox access and modern OAuth authentication. Because this uses a new Microsoft app/API permission set, your tenant may require admin consent again, even if Aqua Mail or older access was previously approved.
Your admins should check Microsoft Entra ID > Enterprise applications and grant admin consent for the Aqua Mail Microsoft Graph permissions required for mail access. This approval is controlled by your organization’s Microsoft 365 security policy and cannot be bypassed by Aqua Mail.
-
Hi everyone,
after the latest update to 2.6.0-043 and switching to graph api, it is no longer possible to add shared mailboxes.
Even the migration of already existing shared mailboxes that were added by EWS in previous aquamail versions could not succeed.
I already granted admin consent for Aquamail in Microsoft Entra and made sure that the following permissions exist:
Calendars.ReadWrite.Shared
Contacts.ReadWrite.Shared
Mail.ReadWrite.Shared
Mail.Send.Shared
So, concerning the permissions everything ist ok in my opinion
Is anyone of you facing the same issues?
Regards
-
Hi everybody,
same issue for me: Can't login anymore via OAuth since update.
I'm afraid I can't use Aquamail anymore.
What other app is still working?
-
Same problem here with the shared mailboxes, and it's a huge issue as that's our on-call mailbox. Adding a shared mailbox just creates a copy of my primary mailbox with the same content. Using Outlook mobile for now to get through the day, but I absolutely hate it compared to Aquamail.
-
The "use current account" setting also seems to be broken. :( It sends from the default account even if composing from a different mailbox.
-
Hi everybody,
same issue for me: Can't login anymore via OAuth since update.
I'm afraid I can't use Aquamail anymore.
What other app is still working?
Found out - these apps are still working with Microsoft OAuth method:
- Thunderbird
- Fairemail
- Gmail
- Outlook (of course)
Any else?
-
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
-
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.
-
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.
-
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.
-
AquaMail version/build: [please fill in from Settings > About AquaMail]
-
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).
-
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.
-
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