Error on Email Tool

[katherinetdavita]

We have a Workflow we've been using for a long time that is suddenly giving an error "Record#1:Func'curl_easy_perform'faled,ret = 56, desc = Failure when receiving data from the peer".

Any idea what this could be due to? See screenshot.

[binuacs]

@katherinetdavita Make sure the email IDs are valid. I've seen this error occur when the system tries to send emails to invalid addresses

[katherinetdavita]

Thanks for this - it's a good tip, but our issue persists even after double checking validity of email adresses.

[binuacs]

@katherinetdavita Are you getting the error when you use a valid email id? I mean use 1 email id and try ?

[katherinetdavita]

@binuacs, yes. have tried my own email as a test, which is definitely valid

[binuacs]

@katherinetdavita okay, then it seems to be a firewall or SMTP issue. Can you try the options below to troubleshoot the problem?

Verify SMTP Settings: Confirm the SMTP server address, port (e.g., 587 for TLS), and credentials in the Email Tool are correct. Test the settings outside Alteryx (e.g., using a tool like Thunderbird or a manual telnet test).
Test Email Server: Try sending an email manually to the same server to see if it’s operational.
Check Firewall/Proxy: If behind a firewall or proxy, ensure port 587 (or the configured port) is open and Alteryx is allowed to communicate.

[katherinetdavita]

@binuacs I'm going to work with IT on some of this. Curious, though: this workflow sends from a shared mailbox. Do you know if the credentials would be my own for my individual M365 account, or would they need to be for the shared box we're trying to send from?
Interestingly enough, we have another workflow sending email successfully from a different shared box, but we're not able to confirm the credentials it's using because they are all ******* in the connection area.

[KGT]

That depends on the settings. If it's a shared box and you have permission to send emails from it, then your credentials should work.

My hunch was that a setting had changed to not allow the SMTP setting (this can happen pretty routinely as a lot of admins don't expect users to be accessing SMTP in a programmatic fashion). However, if another workflow is working, then I don't think it's that. 

Check that you and the other user are on the same version, as it may be outdated cURL libraries for your server config (a change in the MS settings may now only work with a certain version of cURL and the version in your Alteryx may be too old).