Relay host via AWS SES

[IvayLoRD]

What happened?

After we wrote the configurations exactly as described in your documentation, we encountered the following issues, even though the settings are correct and have been made as you instructed, and they appear correctly in the UI.

However, the server is still trying to send emails through the localhost. Even if you click reload on the configurations, the configurations disappear from the config.toml, and still nothing happens. How can I make the server send all emails through SES?

How can we reproduce the problem?

Kubernetes Deployment with

queue.outbound.next-hop.0000.if = "is_local_domain('', rcpt_domain)"
queue.outbound.next-hop.0000.then = "'relay'"
queue.outbound.next-hop.0001.else = false
queue.outbound.tls.dane = "disable"
queue.outbound.tls.mta-sts = "disable"
remote.relay.address = "email-smtp.eu-central-1.amazonaws.com"
remote.relay.auth.secret = "xxxxx"
remote.relay.auth.username = "xxxxx"
remote.relay.port = 465
remote.relay.protocol = "smtp"
remote.relay.tls.allow-invalid-certs = false
remote.relay.tls.implicit = true

Version

v0.10.x

What database are you using?

RocksDB

What blob storage are you using?

S3-compatible

Where is your directory located?

Internal

What operating system are you using?

Docker

Relevant log output

if pod restart and after reload configuration you still have queue.outbound.next-hop in config.toml you got ....

2024-10-09T15:12:48Z ERROR Configuration parse error (config.parse-error) details = "Failed to parse setting "queue.outbound.next-hop": Multiple 'else' found

Code of Conduct

• I agree to follow this project's Code of Conduct

[mdecimus]

You have duplicated entries in the configuration file. If you are using the webadmin to manage the settings then remove the queue.outbound.next-hop entries from the TOML file otherwise you'll have them in two places (the database and TOML file).