Hi:
> The issue is whether the directive is an "operatiorcommand" or a
> "mailcommand". The transport mechanism does not matter (i.e. bsmtp or mutt,
> or whatever). A mailcommand is sent at the end of a job and will include
> all messages generated during the job. The operatorcommand is sent wh
Correct typo of last email:
The issue is whether the directive is an "operatiorcommand" or a
"mailcommand". The transport mechanism does not matter (i.e. bsmtp or
mutt, or whatever). A mailcommand is sent at the end of a job and will
include all messages generated during the job. The operato
The issue is whether the directive is an "operatiorcommand" or a
"mailcommand". The transport mechanism does not matter (i.e. bsmtp or
mutt, or whatever). A mailcommand is sent at the end of a job and will
include all messages generated during the job. The operatorcommand is
sent when the ev
What seems
On Thu, Jun 16, 2016 at 3:35 AM, Kern Sibbald wrote:
> Hello,
>
> There are two things you can do:
>
> 1. Look at the default bacula-dir.conf Messages resource, which avoids the
> problem you are having. You are missing (or probably have deleted) one
> important directive.
>
> 2. Read
Hello,
There are two things you can do:
1. Look at the default bacula-dir.conf Messages resource, which avoids
the problem you are having. You are missing (or probably have deleted)
one important directive.
2. Read the document section on the Messages resource, and in particular
the
"operato
Hello guys:
I'm running Bacula 7.4.0 with a Messages resource like this:
Messages {
Name = Standard
mail = myem...@gmail.com = all, !info, !skipped, !restored, !saved
console = all, !skipped, !saved
append = "/var/log/bacula/bacula.log" = all, !skipped
catalog = all
}
I've just got to
