New M365 Channel using GraphAPI instead of IMAP/SMTP

YetAnotherGerrit · December 9, 2024, 4:06pm

What is your original issue/pain point you want to solve?
Microsoft 365 provides access to their mailboxes using IMAP/SMTP+OAuth or their GraphAPI interface directly. The GraphAPI approach has several benefits for users with Microsoft 365 mailboxes:

No need to manually configure Zammad as an app in the Azure Portal
It still can be used when IMAP/SMTP is disabled tenant-wide
It is faster

Which are one or two concrete situations where this problem hurts the most?
Our service provider decided to disable IMAP/SMTP support for whatever reason.
Why is it not solvable with the Zammad standard?
Because Zammad persist on IMAP/SMTP at the moment.
What is your expectation/what do you want to achieve?
Being able to use GraphAPI for e-mail fetching and sending.

github.com/zammad/zammad

New M365 Channel using GraphAPI instead of IMAP/SMTP

opened 08:17PM - 22 Oct 24 UTC

YetAnotherGerrit

enhancement channel mail processing postmaster filter

**WHY** Microsoft 365 provides access to their mailboxes using IMAP/SMTP+OAut…h **or** their GraphAPI interface directly. The GraphAPI approach has several benefits for users with Microsoft 365 mailboxes: - No need to manually configure Zammad as an app in the Azure Portal - It still can be used when IMAP/SMTP is disabled tenant-wide - It is faster **USE-CASES** An administrator wants to add a Mailbox hosted in a Microsoft 365 tenant. He just clicks an "add M365 mailbox" in the UI of Zammad, the login screen oft M365 opens, he enters credentials and a popup/flyout appears in Zammad asking for the destination group, the folder and if the mails should be kept on the server. **ACCEPTENCE CRITERIA** - Zammad offers the possibility to add Microsoft 365 mailboxes via GraphAPI - Both standard mailboxes and shared mailboxes are supported - No manual app configuration is needed in the Azure Portal, Zammad does that automatically using the GraphAPI-API - The app is generated by Zammad in the scope of the mailbox user if possible - The destination group for that channel can be selected before the first mails are imported - The mailbox folder (tree) can be selected (INBOX is the pre-select) before the first mails are imported - The administrator is asked if he wants to keep the messages on the server before the first mail is imported - Archive mode is working like in the existing mail channels - S/MIME + PGP is supported like in the existing mail channels - Postmaster filter are supported - Trigger are supported - Generally speaking, it should support at least the same functionality compared to the existing mail channels

opinion · December 29, 2024, 8:45pm

I just want to make sure that you know this is highly requested!

Not only does that have the positive effects you provided in the post, it will also save costs, as it will anymore be a requirement to give each shared mailbox a license.