Hello,
I’ve had some issues due to a full temp folder, which I discovered only after two weeks without successful backups. Therefore, I thought, there must be a way to get notified immediately whenever something goes wrong. So I added send-mail to the options of my backup. But I don’t get any mails. I found threads regarding similar problems (
How to set up email notification with Gmail and Setting up email via web-interface not working SOLVED ) and followed the advises but without any success.
Since the web interface did not show any errors, I tried to use the command line interface to get more feedback via:
duplicati-cli --verbose send-mail --send-mail-to="me@gmail.com" --send-mail-username="me@gmail.com" --send-mail-from="me@gmail.com" --send-mail-url=“smtps://smtp.gmail.com:465” --send-mail-password=“crypticPassword” --send-mail-subject=“test”
But using this command, I only get this output:
Input command: send-mail
Input arguments:
Input options:
verbose:
send-mail-to: me@gmail.com
send-mail-username: me@gmail.com
send-mail-from: me@gmail.com
send-mail-url: smtps://smtp.gmail.com:465
send-mail-password: crypticPassword
send-mail-subject: test
Invalid type Microsoft.WindowsAzure.Storage.Blob.BlobEncryptionPolicy for instance field Microsoft.WindowsAzure.Storage.Blob.BlobRequestOptions:<EncryptionPolicy>k__BackingField
Invalid type Microsoft.WindowsAzure.Storage.Queue.QueueEncryptionPolicy for instance field Microsoft.WindowsAzure.Storage.Queue.QueueRequestOptions:<EncryptionPolicy>k__BackingField
Invalid type Microsoft.WindowsAzure.Storage.Table.TableEncryptionPolicy for instance field Microsoft.WindowsAzure.Storage.Table.TableRequestOptions:<EncryptionPolicy>k__BackingField
The output does not change even if I specify an obviously wrong smtp server. However, the invalid type errors indicate that something does not work as intended. But that’s the point at which I don’t get any further using my debugging powers. I found an issue at github Invalid Type errors when calling mono Duplicati.CommandLine.*.exe but according to it, the error should be fixed by version “2.0.2.6_canary_2017-09-16”. Currently I’m on v2.0.2.17-2.0.2.17_canary_2018-01-23.
Any ideas how to resolve these problems?
Best,
Jan