[David Smith]

The smtp:none:none://localhost:25 is an issue for the Outlook 365 plugin, which unfortunately renders this unusable for me. I spend ages trying to resolve this on a DNS level, but it ended being the plugin. Appreciate it is a free plugin ( fully appreciate this) but I can’t wait until the fix is issued, which is a real shame.

I have had to revert to using a paid plugin, which worked perfect. So if you want this working now, then search SMTP on WordPress plugins and its the most downloaded. They do a free version, but if you want Outlook (api) then this does work.

Hope you guys here get the plugin error fixed for Outlook and good luck.

[David Smith]

HI there,

I have an open support post (Email sent successfully but not being being received by emails using 365?), which appears to be narrowed down to this same issue..so seems to be widespread. Very frustrating.

I use a portal plugin that sends a customer a welcome email when I assign them in WP (this works fine, as it uses the amazonsses:443). This email contains a password reset link, which WP sends out (standard WordPress function to reset password). However this email never arrives after they reset because it uses: smtp:none:none://localhost:25.

This is very frustrating as the email never arrives and therefore the registration process fo ray customer can never complete.

Please, can we address this issue – as it appears to be widespread and only for Office 365 emails, which is the majority of mail users.

I hope this gets resolved very soon – in the meanwhile I am being forced to look around for a more reliable SMTP plugin/service.

[David Smith]

Hi Tim,

I was wondering whether you could should any light on the different ‘Delivery URLS’? the smtp:none:none://localhost:25 is being blocked and quarantined but the amazonses.com:443 sends fine.

Why are they sending from different delivery URLs and how can I change the localhost? Does the plugin affect the send URL’s at all?

Thanks in advance

[David Smith]

OK..so I have looked into the email logs and noticed the Delivery URL’s are different with different processes. One of which gets sent fine and and the other gets blocked.

Both of these processes generate a WP email response.

LOST PASSWORD RESET LINK..(DOES NOT ARRIVE AND GETS BLOCKED)
This is a standard WP generated email when users clicks the lost password link.
Delivery URL: smtp:none:none://localhost:25

ADD CLIENT TO PORTAL..(ARRIVES SUCCESSFULLY)
This is a WP plugin but generates a WP email when I assign users to a portal. This sends find to all emails, including Outlook.
Delivery URL: https://amazonses.com:443

Does the Outlook 365 plugin not change the delivery URL for all of the email sent from WP..as the smtp localhost:25 appears to be throwing up issues with Outlook emails.

[David Smith]

I can’t see to post here this morning..Having trouble replying!

[David Smith]

Update: I’ve checked the quarantine and it is being blocked because it doesn’t have a PTR Record?

view the screenshot here: https://ibb.co/Jx05kzq

[David Smith]

Hey Tim,

Thanks for quick reply.

yes, we are sending from an actual 365 mailbox…partners@jitterbyte.com

We did check the SPF records. It appears to affect all Office 365 account. I have only checked two though; one in and one out of our tenancy – as have no other 365 email to check against.

Issue seems to be pointing at 365 emails for some reason?

Thanks,
David

[Author]

Posts