Workaround :
- Gather the current output by running this command on the CB Response backend. Your API token can be found in your user profile in the Response console.
curl -v --tlsv1.2 -XGET -H "X-Auth-Token:<USER_API_TOKEN>" -H "Content-Type: application/json" "https://localhost/api/communication_settings" -k
- Use this output to fill in the information to update the API.
- Copy that full output and put into this post command, changing the email information you need and leaving the "smtp_password": null and "smtp_username": null. All other info should remain the same unless it's being updated.
curl -v --tlsv1.2 -XPOST -H "X-Auth-Token:<USER_API_TOKEN>" -H "Content-Type: application/json" "https://localhost/api/communication_settings" -k -d '{<output here>}'
- As an example, this is how it will look:
curl -v --tlsv1.2 -XPOST -H "X-Auth-Token:<USER_API_TOKEN>" -H "Content-Type: application/json" "https://localhost/api/communication_settings" -k -d '{"smtp_connection_type": null, "statistics": false, "smtp_password": null, "timestamp": "2019-03-18 09:17:11.027580-07:00", "smtp_port": 25, "enabled": true, "smtp_server": 192.168.108.111, "deprecated_community_metadata_only": "off", "ondemand_diagnostics": false, "sensor_diagnostics_mode": 0, "silent": true, "community_participation": false, "mail_server_type": "own", "proxy_url": null, "smtp_username": null, "use_proxy": false}'
- The full output must be given in order for the settings to apply properly.
- Restart the server services, this will reset the email cache
service cb-enterprise restart