Error connecting to SMTP server

[harleygnuya]

When running my nightly VVScheduler backups, I get an error several times a week. I run 7 tasks and have them all email me their completion status. In order to avoid scheduling conflicts, I have them spread out at 1/2 hour intervals.

What happens is that several times a week, one of the tasks will fail to send an email. Which task fails varies, but it is always only 1 out of the 7. When this occurs I open the log file for the task that failed to send the email and this is what it says at the bottom:

2017-10-04 01:30:01 : Sending E-Mail ...
2017-10-04 01:30:01 : Connecting to SMTP server: {my server address}, port: 587, user: '{my email address}' ...
2017-10-04 01:30:03 : [ERROR] Server login failed. Username or password invalid. - 535 5.7.8 Error: authentication failed: PDAxOTI5ODYxNzczNDcwNjUuMTUwNzA5ODYwMEBzbXRwYXV0aDAyPg==
2017-10-04 01:30:03 : Exit Code: 2. Execution not completed. [ERROR]

Looking at the log itself, I see no errors other than the one above.

The SMTP login information is correct and the same as all the other tasks. Which task actually fails varies from night to night. All of them have failed at one time or another, and ones that have failed one night will work the next. I've checked the timestamps for all the tasks and verified that there is no collision.

What is causing the SMTP login to fail? What sort of things should I look for?

Widows 10 Pro 64-bit v1703 build 15063.608
VVScheduler 2.1.0.0
ViceVersa Pro 2.5 Build 2518 64-bit

[TGRMN Software]

Hi, could this be an intermittent issue with the mail server? Or network? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[VXPERT]

Hello,

same problem here. It worked several days, then authentification wasn't suddenly working. Next day it was ok again.

We analyzed the problem and found out, that reason is the authentication method of the integrated mail component in vice-versa which is using Auth-Method "CRAM-MD5" and not "LOGIN" for a secure login.

This seems to be hard-coded in ViceVersa, at least I can not see any option to change the Auth-Method like in many other programs. Moreover, it's a bit obsolete also, see bnsi.net/knowledgebase/business-class-email/end-of-support-for-smtp-authentication-using-cram-md5-1.html.

However, remaining question to ViceVersa is:

How can I change authentication method without disabling secure (SSL-) mail-communication?

Best regards,

VX

[TGRMN Software]

Hi, ViceVersa first tries CRAM-MD5 and if not avail falls back to LOGIN. Is there a way we can try using the SMTP server you are using? thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com