This is not allowed as the title of the posting:
Failed to send message: MailKit.Security.AuthenticationException: AuthenticationInvalidCredentials: 5.7.0 Authentication Rejected (Login incorrect) [6382]
Version: (2.0.4.22_canary_2019-06-30)
Hi,
Probabaly everyone knows, but I only found out after a while of testing.
After setting up sending an email after the backup had finished, I got a warning (1).
At first I couldn’t find where it was shown, because the general log shows no errors and no warnings.
So maybe a tip for future development: clicking the “Show” button goes right in to the message.
At some point I found the warning.
I needed to go to “About” and than “Show Log” than “Live” and finally select “Warning”.
Sep 1, 2019 11:13 AM: Failed to send message: MailKit.Security.AuthenticationException: AuthenticationInvalidCredentials: 5.7.0 Authentication Rejected (Login incorrect) [6382]
{“ClassName”:“MailKit.Security.AuthenticationException”,“Message”:“AuthenticationInvalidCredentials: 5.7.0 Authentication Rejected (Login incorrect) [6382]”,“Data”:null,“InnerException”:null,“HelpURL”:null,“StackTraceString”:" at Duplicati.Library.Modules.Builtin.SendMail.SendMessage(String subject, String body)\r\n at Duplicati.Library.Modules.Builtin.ReportHelper.OnFinish(Object result)",“RemoteStackTraceString”:null,“RemoteStackIndex”:0,“ExceptionMethod”:“8\nSendMessage\nDuplicati.Library.Modules.Builtin, Version=2.0.4.22, Culture=neutral, PublicKeyToken=null\nDuplicati.Library.Modules.Builtin.SendMail\nVoid SendMessage(System.String, System.String)”,“HResult”:-2146233088,“Source”:“Duplicati.Library.Modules.Builtin”,“WatsonBuckets”:null}
So at first I was doubting my credentials, but they where just fine.
After contacting the ISP I got the message that I was trying to use the email address “no-reply@xxx.yyy”.
I didn’t use that email, and it doesn’t exist on the domein either.
So where was it coming from?
Finally by just trying it was used by Duplicati when you do not use a --send-mail-from=xx@yy.zz it uses the no-reply.
Adding a from to the settings solved the issue.
Until 14 days later, but because of the issues probably be of different origin, I’ll make a second post for it.