# Email watcher setup - fail **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [February 19, 2020, 1:33pm UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972 "2020-02-19T13:33:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![RaTheDev](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@RaTheDev](https://discuss.elastic.co/u/RaTheDev)\ **Post date:** [February 19, 2020, 1:33pm UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972/1 "2020-02-19T13:33:07Z")
I am new to WATHER and looking to setup an email triggers for the watchers. Configured my elasticsearch.yaml as directed from ([https://www.elastic.co/guide/en/x-pack/6.2/actions-email.html#outlook](https://www.elastic.co/guide/en/x-pack/6.2/actions-email.html#outlook)) using outlook. Below is the config I used to configure xpack.notification.email.account: outlook\_account: profile: outlook smtp: auth: true starttls.enable: true host: mail.support.local port: 25 user: [support@myorganization.com](mailto:support@myorganization.com) password: \ But attached is the error i am get when starting my Elasticsearch. ![Screen Shot 2020-02-19 at 7.13.16 AM](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0c911ba8d23d41d7dc6b73b2f4605ff233aa5335.png) ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [February 19, 2020, 2:04pm UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972/2 "2020-02-19T14:04:16Z")
Hey, a couple of things: 1. Please don't use screenshots, it's nearly impossible to read. Always paste snippets 2. When using snippets like for configurations, use markdown in here, as this makes it much more readable and the formatting remains as well (which is crucial for YAML). 3. Have you installed the x-pack plugin. You seem to run Elasticsearch 6.2, where you needed to install that plugin manually. From Elasticsearch 6.3 onwards x-pack is always shipped, so you should probably upgrade ---
**Author:** ![RaTheDev](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@RaTheDev](https://discuss.elastic.co/u/RaTheDev)\ **Post date:** [February 19, 2020, 3:21pm UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972/3 "2020-02-19T15:21:16Z")
Thanks Spinscale for a very quick response. I am using Elasticsearch 7.5, so I would guess the x-pack plugin must be installed by default. Here are my configurations ``` xpack.notification.email.account: outlook_account: profile: outlook smtp: auth: true starttls.enable: true host: mail.support.local port: 25 user:support@myorganization.com password: ``` and the error message is as below ``` elasticsearch | {"type": "deprecation", "timestamp": "2020-02-19T13:07:31,467Z", "level": "WARN", "component": "o.e.d.c.s.Settings", "cluster.name": "docker-cluster", "node.name": "afd2f30f327e", "message": "[xpack.watcher.history.cleaner_service.enabled] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version." } elasticsearch | {"type": "server", "timestamp": "2020-02-19T13:07:31,472Z", "level": "WARN", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "docker-cluster", "node.name": "afd2f30f327e", "message": "uncaught exception in thread [main]", elasticsearch | "stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [xpack.notification.email.account.outlook_account.smtp.password] please check that any required plugins are installed, or check the breaking changes documentation for removed settings", elasticsearch | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:125) ~[elasticsearch-cli-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "Caused by: java.lang.IllegalArgumentException: unknown setting [xpack.notification.email.account.outlook_account.smtp.password] please check that any required plugins are installed, or check the breaking changes documentation for removed settings", elasticsearch | "at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:530) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:475) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:446) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:417) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.common.settings.SettingsModule.(SettingsModule.java:149) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.node.Node.(Node.java:352) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.node.Node.(Node.java:253) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:221) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:221) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:349) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.5.0.jar:7.5.0]", elasticsearch | "... 6 more"] } ``` ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [February 20, 2020, 7:36am UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972/4 "2020-02-20T07:36:46Z")
Hey, thank you. It'd be great to fix the indendation issues with the YAML file (as indendation is crucial), but I think I know what the issue is. Instead of using the `password` setting in the YAML file, you need to setup a keystore and use the `secure_password` setting in there. See [https://www.elastic.co/guide/en/elasticsearch/reference/7.6/actions-email.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/actions-email.html) --Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 19, 2020, 7:36am UTC](https://discuss.elastic.co/t/email-watcher-setup-fail/219972/5 "2020-03-19T07:36:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.