----- "Truman Boyes" <[email protected]> wrote: > On 17/02/2010, at 3:57 AM, Phil Shafer wrote: > > > Bill Marquette writes: > >> Is there any way to send email from an op script? > > > > No, sorry. We do snmp, syslog, or transfer, but not email. My > > thoughts were always that email notifications should be done at > > a central server to avoid floods. But this is an increasingly > > common feature request. > > > > Thanks, > > Phil > > You can of course send syslog messages to syslog-ng and have syslog-ng > call mail or a mail wrapper. I would prefer to have simple syslog > messages (ie. log of some event or state) and then have additional > functionality in parsing at a central location.
Sure and we do, but I was trying to build a process that allowed my SRX to push a diff of a given commit back to our ticketing system (which already processes emails) rather than send an event offbox that requires me to then somehow retrieve that change. Yes, I'm aware I can transfer the files, but there are a couple issues with that, the first being transfer-on-commit doesn't appear to support alternate SSH ports, nor does it appear to support RSA private keys, which puts this into an event script at best, the other obvious one is that then I have to process the uploaded files. Working through this, I've decided to save the diff to the local file system and send a trap with the filename for our central server to pick up and pipe it through mailx. Thanks for the input, I'm sure I'll have more questions as I work through writing a SLAX script that encompasses our preferred change workflow. --Bill _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
