• Resolved gb24

    (@gb24)


    I’m using FluentSMTP with multisite directory based (example,com/a, example.com/b, etc.) rather than subsite based (a.example.com, b.example.com, etc.) and authentication with Microsoft 365/Outlook. Did both network activation and also tried individual subsite activation.

    The install, activation, configuraton, and MS365 send mail works fine. However, the callback URL generated for each subsite is different, i.e., it contains the subsite name. Since the callback URL must be configured in the MS365 app configuration, a different MS365 app and secret is now required for each subsite.

    Could you please add a “real” multisite network configuration option to to apply the same global MS365 app id and secret for the main site and all subsites in a multisite configuration?

    Thank you.

    P.S. I’ve tried the option mentioned in this support request without success: https://wordpress.org/support/topic/great-for-multisite-4/

Viewing 3 replies - 1 through 3 (of 3 total)
  • I am also experiencing exactly the same problem with MS 365 callback URLs for multisite.

    Having a different MS 365 app id/callback URL for each subsite is not practical when the same from email is to be used across all subsites.

    • This reply was modified 7 months, 2 weeks ago by ianhman.
    Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @gb24,

    Thank you for reaching out and providing such detailed information about the challenges you’re facing with FluentSMTP and Microsoft 365 in your multisite directory-based WordPress installation.

    As you correctly pointed out, the current design of FluentSMTP uses the full website URL to generate the callback URL, which necessitates individual Azure Apps and tokens for each subsite.

    I can confirm that I’ve forwarded your feedback as a feature request to our development team. We appreciate you bringing this to our attention, as it highlights a significant limitation for multisite setups like yours. We will explore options to introduce a “real” multisite network configuration option that allows you to use a global Microsoft 365 app ID and secret for the main site and all subsites within your multisite network.

    In the meantime, there’s unfortunately no simple workaround within FluentSMTP to achieve what you’re looking for. Implementing a custom solution would likely involve significant code modifications, which is not something we can directly support.

    We appreciate your patience and understanding as we consider this feature request for future development. Thank you for using FluentSMTP!

    Thread Starter gb24

    (@gb24)

    @ibrahimsharif, thank you for the response and confirmation of the feature request.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Multisite Problem’ is closed to new replies.