You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/06/17 02:16:00 UTC
[jira] [Created] (JAMES-3781) As a user I want to enforce explicit configuration
Benoit Tellier created JAMES-3781:
-------------------------------------
Summary: As a user I want to enforce explicit configuration
Key: JAMES-3781
URL: https://issues.apache.org/jira/browse/JAMES-3781
Project: James Server
Issue Type: Bug
Components: guice
Reporter: Benoit Tellier
This one is a fun one!
h1. The postmortem
One of my customer complained of missing emails. After investigations, we found that some emails for alice@domain.org where delivered in #private:alice:INBOX instead of #private:alice@domain.org:INBOX. We then realized that on some James servers of the cluster were configured with virtualhosting off while virtualhosting should have had been on. We then realized the configuration files were moved by an admin. The faulty James servers were not able to locate their configuration files and thus according to JAMES-2004 resorted to the default value with virtualhosting off.
Implicit configuration is nice to ease James onboarding.
But as an operator I would like to have the option to enforce explicit configuration, and have the safety associated with it.
h1. Proposal
Have a JVM property, disabled by default to fail if a configuration file is missing.
`-Djames.fail.on.missing.configuration.file`
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org