issues with notifications

[Lawrence, Lynne]

It looks like you are having quoting issues.  I use a similar notification
command, but my quotes are not escaped.  You might want to try removing the
'\'s preceding each of your double quotes.

Regards,

Lynne Lawrence

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Mark
> Shirley
> Sent: Thursday, June 24, 2004 3:06 PM
> To: pete.dewell at volteurope.com
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] issues with notifications
> 
> 
> define contact {
>     use    admins
>     contact_name    mark
>     alias    mark
>     email    myemail at domain
>     pager    page-me at domain
>     service_notification_period    24x7
>     host_notification_period    24x7
>     service_notification_options    w,u,c,r
>     host_notification_options    d,u,r
>     service_notification_commands    notify-by-email,notify-by-epager
>     host_notification_commands    
> host-notify-by-email,host-notify-by-epager
> }
> 
> my contact template is ...
> 
> define contact {
>     name    admins
>     service_notification_period    24x7
>     host_notification_period    24x7
>     service_notification_options    w,u,c,r
>     host_notification_options    d,u,r
>     service_notification_commands    notify-by-email,notify-by-epager
>     host_notification_commands    
> host-notify-by-email,host-notify-by-epager
>     register    0
> }
> 
> 
> 
> On Thu, 24 Jun 2004 19:37:50 +0100, Pete Dewell
> <pete.dewell at volteurope.com> wrote:
> > 
> > What's the contact definition for this address ?
> > It looks like that has been badly defined in the config file.
> > 
> > Pete Dewell
> > 
> > 
> > Mark Shirley wrote:
> > 
> > > host-notify-by-email
> > > /usr/bin/printf \"%b\" \"***** Nagios *****\n\nNotification Type:
> > > $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress:
> > > $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $DATETIME$\n\" |
> > > /usr/bin/mail -s \"Host $HOSTSTATE$ alert for $HOSTNAME$!\"
> > > $CONTACTEMAIL$
> > >
> > > That is my current host-notify-by-email command.  When a host DOWN
> > > event occurs it says it sends the notification but I never recieve
> > > one.  Upon further investigating I notice in my mail 
> queue a returned
> > > email from my local smtp server stating the following
> > >
> > > From MAILER-DAEMON Thu Jun 24 13:32:53 2004
> > > Return-path: <>
> > > Envelope-to: nagios at helpdesk
> > > Received: from mail by helpdesk-linux with local (Exim 
> 3.35 #1 (Debian))
> > > id 1BdY5l-0002xZ-00
> > > for <nagios at helpdesk>; Thu, 24 Jun 2004 13:32:53 -0400
> > > From: Mail Delivery System <Mailer-Daemon at helpdesk>
> > > To: nagios at helpdesk
> > > Subject: Mail failure - malformed recipient address
> > > Message-Id: <E1BdY5l-0002xZ-00 at helpdesk-linux>
> > > Date: Thu, 24 Jun 2004 13:32:53 -0400
> > >
> > > A message that you sent contained a recipient address 
> that was incorrectly
> > > constructed:
> > >
> > >   my-host.domain.com!"  unmatched doublequote in local 
> part (expected
> > > word or "<")
> > >
> > > The message has not been delivered to any recipients.
> > >
> > > ------ This is a copy of your message, including all the 
> headers. ------
> > >
> > >
> > > To: alert, for, my-host.domain.com!", myemail at domain.com, UP
> > > Subject: "Host
> > >
> > > 
> ""*****""Nagios""*****nnNotification""Type:""RECOVERYnHost:""m
> y-host.domain.comnState:""UPnAddress:""1.1.1.1nInfo:""$nnDate/
> Time:""Thu""Jun""24""13:32:53""EDT""2004n""
> > >
> > > --------
> > > Notice the To: line!
> > >
> > > It seems as though the line it's sending to `mail` is missing some
> > > information.  Could it be that "Host $HOSTSTATE$" is not 
> getting send
> > > to it?  I don't really understand how this could be happening.  Is
> > > there any other information i can provide to make things easier?
> > >
> > > 
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by Black Hat Briefings & Training.
> > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> > > digital self defense, top technical experts, no vendor pitches,
> > > unmatched networking opportunities. Visit www.blackhat.com
> > > _______________________________________________
> > > Nagios-users mailing list
> > > Nagios-users at lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > > ::: Please include Nagios version, plugin version (-v) 
> and OS when reporting any issue.
> > > ::: Messages without supporting info will risk being sent 
> to /dev/null
> > 
> > --
> > 
> > Technical Support/Analyst
> > Volt Europe
> > Tel    : (+44) (0) 1737 774100
> > Fax    : (+44) (0) 1737 772949
> > Mobile : (+44) (0)  777 1513066
> > E-mail  pete.dewell at volteurope.com
> > 
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS 
> when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null