Strange behaviour in Notifications.
in TI 2019 I have 7 different backups, containg either Computer, Volume, or Directory.
All notification control info for the different backups is identical. I created them by using copy and paste from a help file.
All backups target to local H:\<backup name>\
Creating test notifications works well for 6 backups, while it gives an error for one of the directories.
(Translated from German) : Send of test notification failed. Network error. Check the specified e-mail settings.
BTW: I do not see sence in the check mark "store as standard". How can the standard be used in a different backup control?
Peter


- Accedi per poter commentare

Steve Smith wrote:.. assuming that all these tasks are using the same notification settings for the SMTP server, port, user name and password?
Yes, all tasks use exaxcty the same notification:
TO: <me>
REF: "Acronis: %BACKUP_NAME%: %OPERATION_STATUS%"
SERVER: smtp.1und1.de; Port 587; TLS, if possible
SMTP-AUTH.: <me> <password>
No login at the mail input server.
Peter
- Accedi per poter commentare

Peter, after a little playing with settings, I was able to get this working for my own 1&1 account using the settings shown:
- Accedi per poter commentare


pscEx wrote:pscEx wrote:Steve Smith wrote:.. assuming that all these tasks are using the same notification settings for the SMTP server, port, user name and password?
Yes, all tasks use exaxcty the same notification:
Peter
I re-checked the "exactly" and found a trailing blank, not visible in the form, behind the server name of the problematic item.
My fault!
Sorry, Steve for your wasted time!
Peter
- Accedi per poter commentare

I re-checked the "exactly" and found a trailing blank, not visible in the form, behind the server name of the problematic item.
Peter, personally this should have been handled within the ATI code as all programming languages provide functions to strip trailing or leading blanks from strings during processing! I would recommend submitting Feedback with a link to this forum topic to Acronis for this issue - it should be a very simple fix to make!
- Accedi per poter commentare

pscEx, thank you for submitting Feedback, I'll discuss the issue with the product team.
- Accedi per poter commentare