Infos:
Used Zammad version: 2.8
Used Zammad installation source: (source, package, …)
Operating system: Ubuntu Server 18.04 lts
Browser + version: Chrome
Expected behavior:
incoming mails should be associated to correct customer
Actual behavior:
I set up a mailbox (e.g. Helpdesk@mycompanyname.com) in our internal mail system.
zammad is catching the emails from the inbox of helpdesk with imap and creates a ticket in group helpdesk.
That works as expected!
I see the same when using Office365 and aliases attached to the same account. Microsoft sees that the user sending is within the same organisation and changes the TO: header to the primary email address of the mailbox. In the headers the only TO: header is the primary mailbox.
No sorry, i can actually see who sent the ticket with the correct details on the message, but for example
ticketsender@mywork.com emails my Zammad group, then when the ticket is created in the group the customer is set as the group yet next to the message it has ticket senders avatar but if i reply to it then it has the groups email i have to delete the to email of the group and replace it with the correct ticketsenders email
its only where the ticket sender is an agent where this happens
Sorry but I can’t reproduce this, this works perfectly fine on my setup.
What E-Mail-Server are you using.
By the way - you can actually download the EML-File, you should find the needed information there.
Maybe something changes your Mail so Zammad has no choice?
Thanks to KINGRULZ help and access to his installation, I could verify the issue:
This is caused if you send to an Alias of the fetched E-Mail-Account, that is unknown to Zammad.
This issue disappears as soon as you set the alias within E-Mail-Channel.
We’ve already created an bug report for this, please see: https://github.com/zammad/zammad/issues/2414
for further details.