Hello @audunbk,
I’ve taken a close look at the details, and it seems the issue might be related to how the external Outlook service interprets domains with special characters. While you’ve rightly tried the punycode version, some services might still expect a more direct ASCII-equivalent translation in certain input fields.
When domains with special characters (known as Internationalized Domain Names or IDNs) are processed by some systems, they are often converted to their closest ASCII equivalent for broader compatibility. In your case, spørenkristen.no often translates directly to spoerenkristen.no for many services that might not fully support IDNs directly or punycode universally across all their input fields.
Could you please try using the following redirect URL in your FluentSMTP Outlook setup?
https://spoerenkristen.no/wp-json/fluent-smtp/outlook_callback
This version replaces the ‘ø’ with an ‘o’ and ‘e’ together, which often resolves such validation issues with external services expecting a purely ASCII-based domain. Please ensure you replace the existing redirect URL with this specific one in the relevant Outlook application settings where you’re configuring the FluentSMTP integration.
Kindly give this a try and let us know if it resolves the ‘Not a valid URL’ error for you. We’re very hopeful this will do the trick!
Thanks for your advice. I ended up with registering the domain spoerenkristen.no instead, which solved the problem.
