bn tries emailing over-sized logs
If rdiff-backup verbosity is set to -v6 in a backupninja configuration, this sometimes creates very large logs if rdiff-backup fails. One time this happened and backupninja tried sending an email with the entire log, but could not because the system ran out of memory. (It has 16 GB of ram.) I think the memory usage was directly related to log size.
Another time, backupninja successfully created the email, but it did not pass through the mail queue because the message size was about 50 MB.
If anyone else is having this issue, one workaround is to not use the -v6 option with rdiff-backup. : )
It would be nice if backupninja truncated logs to a reasonable size. Since the most relevant errors are bound to occur at the end of the email, running a bytewise "tail" on the message should be sufficient. I figure that 10 KB is more than plenty of log in an email when the user can always check the log file in /var/log/.