Email Tool No Longer Sending Emails Through SMTP That Previously Worked

[elliottwood]

Hi everyone,

I am back with a similar problem I have experienced before. We are currently trying to use the email tool to send multiple emails through our company's SMTP Server. In the past, the unencrypted SMTP settings (Port 25: No Encryption) have allowed us to send out the messages through our company's SMTP (This is after smtp.Office365.com stopped working for Alteryx). However, with the newest update, some staff have begun to receive Curl Errors (Login Denied, Cannot Connect, Timeouts, Ref Error).

Our process worked completely fine on the previous versions and the email tool STILL works with our staff who have Version: 2023.1.1.200 Patch: 1. 

Can anyone help me understand why the newest updates have changed this, and how I can work around this issue for our staff who have mistakenly upgraded and now cannot use legacy workflows? 

Note: Azure Permissions cannot be established per our data policy. So that workaround is not available to us.

Thanks,

Elliott

[elliottwood]

Just wanted to note the below do not work:

smtp.office355.com (Previously Worked)

Port: 587

Encryption: STARTTLS 

smtp.office355.com

Port: 25

Encryption: None

smtp.(ourcompany).com (Previously Worked)

Port: 587

Encryption: STARTTLS 

Authentication: YES and NO (all passwords correct when required)

smtp.(ourcompany).com (Previously Worked)

Port: 25

Encryption: None

[Hamder83]

im pretty sure its because you cant use simpel auth any more:
https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basi...

[JaKael02]

I'm now having the same problem.  That makes sense that Microsoft shut it off, but it's working on previous versions of Alteryx.  So, this must be something related to a recent version of Alteryx versus Microsoft??  

[Hub119]

Since this thread hasn't been marked as resolved yet, in case any of you are still working through these issues (I found this post as I just dealt with this today) you likely are dealing with a problem on the Office 365 side of the fence if you are using multi-factor authentication.  The workaround for this is to create an App Password in your Microsoft account and then use this password in place of your regular Windows/Office password along with your normal username and the rest of your SMTP settings.  Here is the link to the Microsoft documentation on how to go about doing this process:

https://support.microsoft.com/en-us/account-billing/create-app-passwords-from-the-security-info-prev...

Hopefully that helps for anyone who runs into this issue in the future!