Package: keepalived
Version: 1:1.2.2-2
Severity: normal

In keepalived.conf.SYNOPSIS.gz the example code shows how to enter the 
recipient email address like this:

    notification_email {                # Email to send alertes to
       <EMAIL ADDRESS>                  # Standard email address
      <EMAIL ADDRESS>
      ...
    }

In the manpage the opening curly brace is in an extra line.

    notification_email    # To:
         {
          [email protected]
          ...
         }

The first example works.

The manpage example basically works too.
But only as long as you keep the "# To:" in the line.
If you remove it, the parser will treat '{' as a recipient address.

By this the SMTP server rejects the delivery attempt and keepalived writes the 
following lines into its logs:

Jan 20 13:50:05 mailclient Keepalived_vrrp: Error processing RCPT cmd on SMTP 
server [x.x.x.x:25]. SMTP status code = 501
Jan 20 13:50:05 mailclient Keepalived_vrrp: Can not read data from remote SMTP 
server [x.x.x.x:25].



SMTP chat looks like this (Exim used on server-side):

S: 250 mailserver Hello mailclient [x.x.x.x]
C: MAIL from: <[email protected]>
S: 250 ok
C: RCPT TO:<{>
S: 501 <{}: recipient address must contain a domain

Cheers,
Andreas

-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages keepalived depends on:
ii  iproute                 20100519-3       networking and traffic control too
pn  ipvsadm                 <none>           (no description available)
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libpopt0                1.16-1           lib for parsing cmdline parameters
ii  libssl0.9.8             0.9.8o-4squeeze5 SSL shared libraries

keepalived recommends no packages.

keepalived suggests no packages.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to