Settings: Server smtp.google.com Port 465 Encryption SSL From Googlemail address Server requires authentication Yes login googlemail. address Password googlemail password Sending test email fails, saying auth-method is PLAIN It goes on to say that it cannot resolve hostname which it f=defines as smt...

Yes, that seemed the most likely, so it is what I have been doing.

The error message says "SMTP server replied: ChilkatLog". Googling suggests that this means authentication is being attempted without security settings - and sure enough the logfile says StartTLS: 0 I know that gmail will not accept messages without StartTLS set to !, so how can I change this? Anne

No, it's not two-step verification. I'm not even clear which password I'm supposed to give. It seemed likely that it wanted the smtp.google password, but I've also tried my local user password. I can see from the logs that Backup4all is trying to send the emails, so it has to be my configuration of ...

Here is a part of the log file, which I hope will show someone what my problem is: Secure Channel Established. Turning on TCP_NODELAY. socketOptions: SO_SNDBUF: 65536 SO_RCVBUF: 65536 TCP_NODELAY: 65537 --socketOptions socketConnect: Elapsed time: 109 millisec SmtpCmdResp: 220 smtp.<url removed> ini...

Support wrote: > Hi, > > Do you have this problem every time you run the backup? > As the log file is not complete, is the error about the Backup4all.hst file? > In such a case you can close Backup4all and rename the "Backup4all.hst" file. Do > you still have the problem after that? The problem only...

Since my major reorganisation of my server (and simultaneous update of Backup4all) I find I am not getting emails signifying completion status. It was necessary to make large changes to my backup jobs, creating some new ones as well. I suspect that I have given the wrong credentials for sending emai...

In fact it almost certainly was the same problem as last time. The difficulty is that there is no easy way of knowing where the backup was looking when it found something it couldn't handle. The only way, I think, is to greatly reduce the size of the backup initially, then painstakingly go through e...

Apparently I had a similar sounding error, last year. In that case it was caused by filename conflicts - eg. upper case/lower case versions of the same filename. I don't think it is the same problem this time so here is some additional information about this particular backup. I have just expanded a...

[15/06/2016 00:03:07] Error: SQL error "m_hStmtTmpFlsVerExcl" - SQLite_Finalize, library routine called out of sequence (21) (SQL04) [15/06/2016 00:03:07] Closing file "C:\Users\Anne\AppData\Roaming\Softland\Backup4all 6\Backup4all.hst" This is beyond my knowledge level. Is there anything I can do a...