2 @section Configuration notification options
4 That section controls what notifications are enabled and how must be
5 sent through the email. Notifications are sent for successful tossing of
6 file, freq or exec packet.
12 to: user+file@example.com
16 to: user+freq@example.com
20 from: nncp+bob@localhost
21 to: user+somehandle@example.com
25 to: user+anotherhandle@example.com
31 Corresponding @strong{from} and @strong{to} fields will be substituted
32 in notification email message. @code{neigh.self.exec.sendmail} will be
33 used as a local mailer (command called for sending email message).
35 You can omit either of those two @code{from}/@code{to} sections to omit
36 corresponding notifications, or the whole section at once.
38 @code{notify.exec} section is a mapping of exec handles and
39 corresponding @code{from}/@code{to} sections. Each handle has either
40 @code{NODE.HANDLE} or @code{*.HANDLE} syntax. You can override
41 notification options for some node with the first type of name. Handle
42 command's output will be included in notification messages.