Issue
Rather than using an installed email client on your computer, Foxtrot RPA uses your SMTP server to send emails and your IMAP server to receive emails. In order to do so, both the configuration on the server side and the email preferences in Foxtrot RPA must be set appropriately. Error 5 indicates that the server itself is rejecting the connection.
There are a variety of different errors within Error 5 that can occur.
Response Code:
- 4.3.2 - indicates that the server is busy and cannot deliver messages at this time
- 5.7.57 - SMTP: The Client was not authorized to email anonymously during MAIL FROM.
- 5.7.1 - Client was not authenticated
- Failure to send mail.
- The operation has timed out.
- 4.3.1 - indicates the attachment exceeds the allowed size in the email setup.
Resolution
For all of these codes and server responses, there are a few basic things to check.
Within your project’s email connection:
- If you require authentication, verify your email and password are correct. Remember that your email login may be different from your Windows login information.
- Check your SMTP server and IMAP server information. Ensure the server address, port, and SSL options are correct.
- Check to see if the maximum attachment size is exceeded. If your IT department says it is not, ask if there is a mail relay because that will have a size maximum as well and could be lower than the what is in the email settings.
If you are still receiving an error message after checking everything within your project is correct, it is time to contact your IT department. They will need to verify the following the following:
- On your workstation, ensure no virus scanners or firewalls prevent emails from being sent through 3rd party applications.
- Check that third-party programs can send emails on the SMTP server. If not all, Foxtrot RPA LE should be on a whitelist of programs that are allowed to send emails.
- On the SMTP server, make sure the workstation that the action is failing on is allowed to send emails
- On the SMTP server, ensure the Windows login that the action is failing on is allowed to send emails.