Zammad re-imports all mails after M365 re-authentication

Infos:

  • Used Zammad version: 5.4.0-1680612797.66e35235.centos7 but occured in previous version as well
  • Used Zammad installation type: source
  • Operating system: Centos7
  • Browser + version: Any

Expected behavior:

  • When a Mailbox reports an authentication error ({FA4F3FDE-1CF5-4A13-B8AD-4CAA07FF844B}
    ), we re-authenticate the mailbox
  • Authentication is handled by Microsoft
  • Zammad can access the mailbox again and checks for new, unread mails

Actual behavior:

  • We re-authenticate the mailbox, handled by Microsoft
  • Zammad starts import all mails from the mailbox’s inbox, whether the mails are read or unread even if the same message-id was previously imported already

Steps to reproduce the behavior:

  • In our instance: re-authenticate a mailbox
  • Logs don’t provide any information that hint towards this behaviour, simply stating that the mailbox will be checked for new messages and starts importing all messages

Has anybody else experienced this behaviour before or has any ideas on how to mitigate this? Deleting the mails from the mail server after importing into Zammad might just be our next step to prevent this from happening again. It isn’t set up to delete mails after importing them at this time.

This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.