Issues with smtp refusing to connect

billy_wotherspoon

Hi all,

Been getting this error
Warning: stream_socket_client(): unable to connect to 40.100.174.210:590 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ) in C:\inetpub\wwwroot\include\pear\Net\Socket.php on line 166

This happens anytime i try and set up replies via SMTP

The picture above indicates to me that it is a PHP issue but I dont know if that is true nor what I should edit to make it work

Any help would be much appreciated

RBGE

billy_wotherspoon I'm fairly convinced MS 365 doesn't allow anonymous SMTP connections, and the default port to use is 587. See the screenshot of my settings below:

ntozier

I /agree with RBGE

billy_wotherspoon

RBGE

Says auth is disabled when It has been explicitly enabled for this mailbox via powershell

RBGE

billy_wotherspoon Okay, if SMTP Auth is disabled at your tenant then that means SMTP is disabled, not authentication, so it still won't connect with no authentication set. If you've enabled it via Powershell, does it show as enabled via the admin console? ( https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission#enable-smtp-auth-for-specific-mailboxes ) Does it show up if you use the Get-CASMailbox example script on that same page to return SMTP Auth enabled mailboxes?

It sounds like the setting hasn't saved, although we don't have SMTP Auth disabled at the tenant level on our setup so I can't even try to replicate your situation I'm afraid.

Port is definitely correct at 587 though!

billy_wotherspoon

Hi,

Got this fixed now just trying to get the ad/ldap plugin to work.

Thanks for the help

RBGE

billy_wotherspoon Excellent, good to hear. Did you work out what the problem was, just in case someone else with the same issue finds this post at a later date?
AD plugin should be fairly straightforward too, it just needs a DC to query and an account to authenticate with.

billy_wotherspoon

Hi Turns out it was an O365 command I had to run which is on thier website to allow the email account to use it