gotschi
November 11, 2024, 8:40am
1
Used Zammad version: 6.3.0-1714467514.a5110336.jammy
Used Zammad installation type: (source, package, docker-compose, …): package
Operating system: Ubuntu 22.04
Browser + version: MS Edge 130.0.2849.80
Expected behavior:
I createt a Microsoft 365 Channel for sending Emails by Trigger and Standard Notification.
Actual behavior:
Trigger Emails work perfect but standard notifications not.
Steps to reproduce the behavior:
Tried to subscribe a ticket, but never recived a standard notification.
Zammads notifications are not sent via regular email channels (this includes Microsoft 365 and Google channels). Our documentation clearly states, that these channels currently are not supported for notification sendout.
Zammad has a notification channel that is used for these mails.
Hello,
so I have the same Problem. MS ist shutting down SMTP Auth is there a best practice to get Notifications via E-Mail?
Is the Implementation on the Roadmap?
Thank you
A very quick and small search could have answered your question.
Allow OAuth-connected Google/Microsoft mailboxes to be used for Notification by Email (opt-in with guardrails)
I believe this is a bug in the product’s design. I opened a GitHub issue Cannot send Email Notifications when primary mailbox is Google (OAuth) #5731 which was closed as “not planned.” Closing it doesn’t address the underlying inconsistency: Zammad can send ticket traffic via an OAuth-connected mailbox, yet refuses to use the same authenticated transport for Notification by Email , forc…
No workaround except abusing triggers. Zammad generally doesn‘t communicate ETAs nor Roadmaps so who knows.
Thank you MrGeneration for your quick and small search. I will then use our internal E-Mail Gateway as a SMTP Relay for Zammad.
Nevertheless Thank you for the fast Reply