# XPack Email From not Being Updated by Cluster Update Settings API
**URL:** https://discuss.elastic.co/t/xpack-email-from-not-being-updated-by-cluster-update-settings-api/144536
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [August 15, 2018, 3:22pm UTC](https://discuss.elastic.co/t/xpack-email-from-not-being-updated-by-cluster-update-settings-api/144536 "2018-08-15T15:22:10Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ryanrossiter](https://discuss.elastic.co/u/ryanrossiter)
#### Post date: [August 15, 2018, 3:22pm UTC](https://discuss.elastic.co/t/xpack-email-from-not-being-updated-by-cluster-update-settings-api/144536/1 "2018-08-15T15:22:11Z")
Hi, my cluster has an `xpack.notification.email.account` configuration in its `elasticsearch.yml` file, and email notifications are working fine with it, but when I update the "from" address using the Cluster Update Settings API like this (the email profile is called account):
```
PUT {
"persistent": {
"xpack.notification.email.account.account.email_defaults.from": "NEW_ADDRESS@HOST"
}
}
```
I can see that the setting was applied when running `GET` on the API but new notifications still come from the previous email. Why doesn't the new email address get used?
---
### Author:  [@ryanrossiter](https://discuss.elastic.co/u/ryanrossiter)
#### Post date: [August 15, 2018, 3:48pm UTC](https://discuss.elastic.co/t/xpack-email-from-not-being-updated-by-cluster-update-settings-api/144536/2 "2018-08-15T15:48:57Z")
Oops, nevermind. After searching through the Elasticsearch log I can see that the email I provided to override with contained an illegal character and was rejected.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 12, 2018, 3:49pm UTC](https://discuss.elastic.co/t/xpack-email-from-not-being-updated-by-cluster-update-settings-api/144536/3 "2018-09-12T15:49:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.