When a ticket reply is sent from zammad and received by the recipient, the From: field uses the Display Name configured in Microsoft 365/Exchange Online
Is this a bug or configuration error in Zammad or is this a restriction when using the MS365 Graph Api Channel? Nevertheless this is currently a showstopper for us.
Did you obeserve something similar with other Tenants? Or is it only affecting our MS365 Tenant? I know this was working with MS365 IMAP Channel before…
From Zammad perspective the same code is used like for the user email channels. So could really be something on Microsoft side. You could maybe check the generated raw mail from the outgoing article.
did so already, the raw mail shows indeed From: Marco **** via **** Support <ticket@****.**>.
For the moment I reverted back to IMAP/SMTP. So it seems to only affect the Graph Api. Did you observe similar behaviour in other tenants? Currently I am out of ideas which setting could affect this on 365 side.
Has anyone tested this in the meantime? Is it still the case that the display name from the shared mailbox is shown, and not the display name assigned by zammad?
No, I am currently not able to verify if this is still the case as we are using IMAP/Oauth for the moment.
Just for clarification, my problem was not about using e-mailaliases, it’s the displayname which is changed to the MS365 Value instead the “From:”-Value when using the Microsoft 365 Graph channel.
We identified already that it’s not a problem on Zammad side, because the generated mail has the correct from value (I think it was mentioned in another thread). So sometimes it seem to be outlook is showing it differently because of address book entries or other things.
Yes, correct, this seems to be a problem (“feature”) in MS365 rather than in Zammad. But it has nothing todo with Outlook address book entries as I could reproduce the behaviour with an gmail recipient which never received an email from my zammad instance before.
Maybe I will try to reproduce the problem by just issuing a small powershell script using the graph api to isolate the problem to MS365 so I can open a support case with MS…