Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to change the subject if the backups is not completed? #110

Closed
planetahuevo opened this issue Aug 7, 2017 · 5 comments
Closed
Assignees
Milestone

Comments

@planetahuevo
Copy link
Contributor

I am getting daily emails for my backups, which is working great.
Sometimes my backup fails because it cannot upload it properly to the S3.
It is not a big issue and I am working to use smaller backups to fix it, but it could be a great enhancement to provide a different subject on the email if the Backup failed for anything or if the backup has been a suceded.

That way I can filter them on my email and only get into my inbox the important ones: the failed ones.

Thanks!

@sebastianfeldmann
Copy link
Owner

I added a state flag to the mail title [OK|WARNING|ERROR]

This will be released with version 5.0.0

@planetahuevo
Copy link
Contributor Author

Hi,
I cannot find this on the docs.
Can you put an example on how to use it?
Thanks!

@sebastianfeldmann
Copy link
Owner

sebastianfeldmann commented Aug 30, 2017

The email subject will always have different suffixes.

"Backup report from example.com [OK]" (all good)
"Backup report from example.com [WARNING]" (backup ok but sync cleanup... failed)
"Backup report from example.com [ERROR]" (backup failed)

You can customize your subject line.

<option name="subject" value="My Backup Subject" />

This will result in subjects like
"My Backup Subject [OK]"
...

Hope that helps.

@planetahuevo
Copy link
Contributor Author

It does help. Thanks!

@sebastianfeldmann
Copy link
Owner

Nice ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants