Troubleshooting issues occurring during the setup process

From Hornbill
Jump to navigation Jump to search

In the event that problems occur during the setup process. These are some of the problems that have been encountered, and the solutions to them.

  1. The credential window and the consent window are endlessly presented.

    Description: After connecting the keysafe entry to the desired email account, and the admin consenting to the operation, Microsoft once again asks for the desired email address and the consent. The whole operation is repeated once again.

    To solve this issue, the following steps are suggested:

    1. Ensure that the "Hornbill Office365 Mail Connector" is not present in the list of Enterprise Application
    2. Ensure that the target Keysafe entry is unconnected.
    3. Temporarily connect the keysafe entry to a global admin account with an empty mailbox.
    4. Setup the IMAP4/POP3 email service with the global admin account.
    5. Ensure that the email can get into the mailbox.
    6. Once successful, revoke the keysafe entry and connect to the desired email address.
    7. Setup the all the necessary connectors as they should now be properly enabled.
  2. No emails are being received, and the following error always appears in the EspMailImporter.log.

    Description: Upon completing the connection and setup of the shared mailbox, the following error "serverResponse: aaac BAD User is authenticated but not connected." is logged in the EspMailImporter.log log file. Mail is also not being delivered to the shared mailbox.

    • To solve this issue, the following steps are suggested:
    1. Ensure that the "Hornbill Office365 Mail Connector" is not present in the list of Enterprise Application
    2. Ensure that the target Keysafe entry is unconnected.
    3. Temporarily provide the desired email account with the following azure role/privileges:
      • Application Admin
      • Exchange Admin
    4. Connect the target Keysafe entry to the desired email account
    5. Setup the IMAP4/POP3 email service with the desired email account/target Keysafe entry.
    6. Ensure that the email can get into the mailbox.
    7. Once successful, revoke/remove the azure role/privileges:
      • Application Admin
      • Exchange Admin
    • Another possible solution is ensure that the required protocol is enabled either in