gilad404
Forum Replies Created
-
YES! On my end, the business site stays up on 4.0.1. Thanks for the quick fix 👌🏻💯
I’m willing to contribute, but I am no developer and I don’t have any staging, local or backup site to try beta releases on.
Auto Update is turned off for this plugin right now – I can recheck for issues when the next STABLE release comes out. If you prefer receiving issues about stable releases by Email, go ahead and contact me there.
I can also able to keep following this thread for updates related specifically to Elementor compatibility.
Update: editing a post in the regular WordPress block editor works completely fine. I’ve network-enabled the plugin, edited an existing post, clicked Save, got a message that the post was updated, then double checked by navigating to the actual post in the Front-end. Now I’ve network-disabled the plugin again.
Just hopped in to check for updates.
The new deadline from MS is 2026-03-01, according to the following updating post https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750
Also, I have found that many WP SMTP plugins use ‘https-example-com/wp-admin’ as a redirect URI when sending through Outlook. Since this address does not contain a query string, it plays nice with all permalink structures, including the default ‘ugly’ one. This is what I came up with in my search:
Plugins that use the wp-admin subdirectory:
- https://wpmailsmtp.com/docs/how-to-set-up-the-outlook-mailer-in-wp-mail-smtp/
- https://postmansmtp.com/connect-microsoft-outlook-to-wordpress/
- https://www.gravityforms.com/blog/how-to-send-wordpress-emails-with-microsoft-365-outlook/
- https://easywpsmtp.com/docs/setting-up-the-outlook-mailer/
Other options:
- GoSMTP – uses a wp-gosmtp subdirectory, similar to wp-admin: https://gosmtp.net/docs/gosmtp-mailers/microsoft-365-outlook-pro/
- miniOrange – uses the domain name without any subdirectories: https://plugins.miniorange.com/how-to-send-wordpress-emails-using-microsoft-graph-api
I have also found that many 3rd party guides on sending Emails through WP+365 recommend WP Mail SMTP, so I would suggest treating their approach as a best practice.
I’ve Googled: wordpress smtp outlook return uri
I hope that helps shorten times.
Please DO NOT mark this thread as resolved until an actual long-term fix is published in production. Leaving the conversation open should attract more users to join and suggest ideas, making the resolution process quicker and more comprehensive, as it should be in open source 💪🏻
- This reply was modified 10 months, 2 weeks ago by gilad404. Reason: added '+365' for 3rd party guides subject
Thanks for the fast reply 👌🏻
A feature request is the perfect long-term solution:
- I will be happy to provide additional information if needed.
- I’m attaching a link to an official post from MS regarding the planned deprecation of basic SMTP: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH). The deadline is September 2025 with no clear day of the month.
- Please note that MS may not be the only provider with such constraints for Callback URIs. I would suggest to check all the providers you work with to avoid duplicate work and make the request more comprehensive.
Meanwhile I will:
- Keep using ‘Other SMTP’ in WP Mail SMTP – it already works and requires zero alterations.
- Disable FluentSMTP until a fix is published.
- Keep following this thread.
Thanks again 💪🏻
Asking the user to change their site’s link structure may be helpful for a new site, but for an established site with many inbound links that were built over years, that is an SEO disaster and therefore clearly out of scope.
By now I have already managed to add redirections in .htaccess but Azure won’t accept them. Their validation system expects the exact redirect URI sent in the request to match one listed under ‘Manage’ – ‘Authentication’. Any rewrite, no matter how transparent to the user or browser, results in a mismatch error.
Instead of accusing users for using a WordPress default setting and MS for denying certain URIs for security reasons (possibly many more providers do so), the change has to be on the plugin’s side: Let the plugin internally alter the Redirect URI when detecting a Plain permalink structure. Display the updated URI to the user during setup under the regular ‘App Callback URL’ caption so all the addresses stay consistent on both WP and the provider.
I currently send emails through 365 using WP Mail SMTP with the legacy SMTP authentication method (“other SMTP”). That should work until September 2025. Considering FluentSMTP is the only free option I have found in the WordPress plugin directory for sending emails through 365 OAuth, many more users will turn to FulentSMTP and possibly face the same problem.
Thanks in advance 👍🏻
The snippet on my side looks different:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
#RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress.htaccess contains ‘mod_rewrite’ but in another place, outside this snippet.
How should the updated snippet look like? Will that require also changing the link structure?
Forum: Plugins
In reply to: [oEmbed Plus] Facebook App Review rejects my oEmbed URLUpdate: A human from Facebook App Review Support (https://www.facebook.com/379586999318427/) told me to switch the app from live mode to development mode and to ensure I have an administrator role in the app settings. I did both and embeds still not work.
Please note that the app domains are defined and all of my requests come from them.
This is all the documentation I found on development mode. very confusing.
https://developers.facebook.com/docs/development/build-and-test/app-modes#development-modeThanks 🙂