Tommy Atkinson and Sylvain Faivre reported that email alerts didn't work when
they were declared in the defaults section. This is due to the use of an
internal attribute which is set once an email-alert is at least partially
configured. But this attribute was not propagated to the current proxy during
the configuration parsing.
Not that the issue doesn't occur if "email-alert myhostname" is configured in
the defaults section.
This fix must be backported to 1.6.
---
src/cfgparse.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/cfgparse.c b/src/cfgparse.c
index 44070a5..9ebae2c 100644
--- a/src/cfgparse.c
+++ b/src/cfgparse.c
@@ -2804,6 +2804,7 @@ int cfg_parse_listen(const char *file, int linenum, char
**args, int kwm)
if (defproxy.email_alert.myhostname)
curproxy->email_alert.myhostname =
strdup(defproxy.email_alert.myhostname);
curproxy->email_alert.level = defproxy.email_alert.level;
+ curproxy->email_alert.set = defproxy.email_alert.set;
goto out;
}
--
2.6.2
