Versions Compared

Version Old Version 12 New Version Current
Changes made by

Mike Harrison

Denny Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. From the top right of the screen, select Create

    image-20240902-073905.png

  2. Click Sign in with Microsoft

  3. Select any optional permission scopes you want to grant to JEMH Cloud and click OK. If you are planning on using a shared mailbox, you’ll want to consent to the optional permission shown. See Using an Inbound shared mailboxesmailbox for more information.

    image-20240902-074135.png

  4. At this point, you may be asked to grant consent to JEMHC acting on behalf of the signed in user. See the previous section on granting consent for more information.

  5. After granting consent to the request, a screen confirming successful authorization is shown:

  6. Returning to JEMHC, you should now see the new connection:

     

  7. Clicking the green ping icon will then test the connection. A successful test will look similar to this:

     

  8.  The mail connection is now ready for use. These steps are identical for setting up both Message Sources and Message Outbounds.

...

We have (at the time of writing) an open ticket with Microsoft regarding the problem, that the request is returning a 202 Accepted response and a Retry-After header value. Due to this external bug, our solution has been to currently inhibit the retry attempts, as the initial request to send the mail is successful.

Message outbound offline due to “The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending account”

SimpleHttpClientException “The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending account”

If the message outbound connection is no longer able to send emails as the configured sender, Microsoft 365 may return a 403 response.

This could be due to:

  • Existing configuration/OAuth no longer being valid (E.g. if the configured Outbound was set up using a User account that has since been removed/restricted external sendMail permissions).

  • Existing configuration has been edited to send using a new sender address. (If the new sender address does not have the relevant sendMail permissions, the outbound message configuration may still fail).

It is recommended to revisit your JEMHCloud Outbound Message configuration in order to understand why the connection is failing. Re-authorizing with an account that has the correct permissions will fix the problem.