Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixes #676 - Added another error message for M365 (authentication unsuccessful) #678

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Fixes #676 - Added another error message for M365 (authentication unsuccessful) #678

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions channels/microsoft365/common-errors.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,3 +169,20 @@ To avoid this, you should change the
`Safe Attachments unknown malware response <https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-about?view=o365-worldwide#safe-attachments-policy-settings>`_
from "Dynamic Delivery" to something else fitting your needs (e.g. "Block") for
your Office 365 instance.


Authentication Unsuccessful
---------------------------

**Error message:** 535 5.7.3 Authentication unsuccessful

.. note:: This error message can have different reasons. See description below
for one of them.

Microsoft allows sign-in and authentication using the primary email address.
While this works for fetching emails, SMTP authentication may not work in this
case.

Try to delete the MS account and recreate it using your username.
In Zammad, manually change the email address to the username. Then you should
be able to send and receive emails again.
22 changes: 21 additions & 1 deletion locale/admin-docs.pot
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Zammad Admin Documentation pre-release\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-10-07 18:05+0200\n"
"POT-Creation-Date: 2024-10-22 11:54+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
Expand Down Expand Up @@ -4048,6 +4048,26 @@ msgstr ""
msgid "To avoid this, you should change the `Safe Attachments unknown malware response <https://learn.microsoft.com/en-us/defender-office-365/safe-attachments-about?view=o365-worldwide#safe-attachments-policy-settings>`_ from \"Dynamic Delivery\" to something else fitting your needs (e.g. \"Block\") for your Office 365 instance."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:175
msgid "Authentication Unsuccessful"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:177
msgid "**Error message:** 535 5.7.3 Authentication unsuccessful"
msgstr ""

#: ../channels/microsoft365/common-errors.rst:179
msgid "This error message can have different reasons. See description below for one of them."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:182
msgid "Microsoft allows sign-in and authentication using the primary email address. While this works for fetching emails, SMTP authentication may not work in this case."
msgstr ""

#: ../channels/microsoft365/common-errors.rst:186
msgid "Try to delete the MS account and recreate it using your username. In Zammad, manually change the email address to the username. Then you should be able to send and receive emails again."
msgstr ""

#: ../channels/microsoft365/email-headers.rst:3
msgid "Header based actions in Microsoft 365 channels work in the same way as in email channels. This is why the section has been adopted verbatim from :doc:`here </channels/email/email-headers>`."
msgstr ""
Expand Down
Loading