Use of config file

[steini86]

Hi, thanks for the fantastic project!
I am using the bare linux executable but I would like to not have the imap password in the command for several reasons (process name, history,..). Is it possible to use a config file to store the options?
Thanks!

[cry-inc]

Currently only command line and ENV variables are supported. Support for an additional config file is currently not planned. Would consider this request if its becomes common and more people are asking for it.

Maybe ENV variables can help with your use case? Consider a small script like this one:

export IMAP_HOST="mail.server.com"
export IMAP_USER="dmarc@server.com"
export IMAP_PASSWORD="imap-password"
export HTTP_SERVER_PASSWORD="http-password"
./dmarc-report-viewer

This keeps the private values away from ps and similar and they do not show up in the bash history. You can run ./dmarc-report-viewer --help to get the names of all the possible ENV setting names.

[ffried]

Just adding my vote here with another use case: Docker (or Kubernetes) secrets and configs.
Some Kubernetes environments even prohibit linking secrets as environment variables.

But instead of a separate config file, most services simply accept _FILE suffixed env vars (e.g. IMAP_PASSWORD_FILE). We've previously implemented this by simply checking the file suffix variant first, and falling back to the normal one.