- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyNas 212 OS 6.10.7 no longer sends emails
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNas 212 OS 6.10.7 no longer sends emails
I don't know why but my ReadyNas no longer sends emails after a backup job. Even if the job failed.
And there is no report in msmtp.log
I checked and re-validated the email settings, and I received the test email.
And for the test, there is indeed a report in the log file.
So, I was thinking of reinstalling firmware 6.10.7 to see if that solved the problem.
What do you think and is there a risk?
Unless you have other ideas...
Thanks,
Olivy
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 212 OS 6.10.7 no longer sends emails
Have you checked the backup settings under option?Have you tried changing the settings and reverting it back to full backup logs? If you already did and still getting the same issue, an OS-reinstall might help though few settings will be back on default state such as Network and Admin settings.
HTH
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 212 OS 6.10.7 no longer sends emails
Yes I tried all of that.
So reinstalling the same firmware only resets network settings and admin password? Nothing else like users, backup job...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 212 OS 6.10.7 no longer sends emails
@olivy wrote:So reinstalling the same firmware only resets network settings and admin password? Nothing else like users, backup job...
It also turns off volume quota, which you can re-enable. Click on the volume settings wheel on the volume tab, and then choose "settings". You'll see quota there.
User accounts, data, backup jobs are not affected.
FWIW, I would create a test backup job first, and set it to always send an email. Then see if that works as expected. If it does, then I'd next delete the problem backup job and re-create it.