Page tree
Skip to end of metadata
Go to start of metadata

 

 

This page has moved 

  • No labels

4 Comments

  1. Shouldn't be:

    # Customization: all of the "asterisk" user's mail should be directed to a monitored e-mail address
    asterisk: root
    root: myemail@domain.org

    instead of:

    # Customization: all of the "asterisk" user's mail should be directed to a monitored e-mail address
    asterisk: myemail@domain.org

    as per FREEPBX Ticket number 5751 (Ticket number 5754, as reported per link's text above, results wrong but the link goes effectively to FreePBX Ticket number 5751...it seems a shift of three from old trac site).

  2. Hi parnassus, the root user gets other system-related e-mails not from the FreePBX backup system, such as mdadm RAID monitoring or other system event e-mails. It's a best practice to have the root account deliver e-mail to a human being. So, the original above sends mail to the local asterisk user to root instead, and then sends all e-mail to root (including whatever was sent to the asterisk user) to a monitored e-mail address.

  3. Hi Tim, yes I understood how aliases work. I just noticed that what's on this wiki page differs from what was written on the FreePBX Ticket 5751 (here taken as a link to read as reference) in which asterisk user is aliased (let me use this term) to root and then root is finally aliased to a monitored external e-mail address.

    I don't know if one (asterisk -> root -> external monitored e-mail address) is better than other (asterisk aliased directly to an external monitored e-mail address excluding root which isn't aliased at all): sure that the second doesn't let system notifications to flow externally...but, in both cases, the important thing is that notifications flows and eventually system admin could then change aliases behaviour accordingly.

  4. Ohh, I see what you mean. The root user is not included in the wiki page but is in the ticket. I will edit the wiki to suggest this. Thanks.