Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helo checks config settings misbehave #1832

Closed
msimerson opened this issue Feb 21, 2017 · 0 comments
Closed

helo checks config settings misbehave #1832

msimerson opened this issue Feb 21, 2017 · 0 comments

Comments

@msimerson
Copy link
Member

system info

Haraka Haraka.js — Version: 2.8.13
Node v7.3.0
OS FreeBSD haraka 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016 [email protected]:/usr/obj/usr/src/sys/GENERIC amd64
openssl OpenSSL 1.0.1s-freebsd 1 Mar 2016

Expected behavior

For helo.checks to behave as documented: by default all checks are enabled, all rejects are disabled. That's what the .md file claims and it's what the default helo.checks.ini file contains, but it's not what the defaults are in helo.checks.load_helo_checks_ini()'s boolean declarations.

Observed behavior

Despite [reject]valid_hostname=false being set in the default config file, and that setting not being present in the local overrides file, that rejection option ends up being enabled.

Steps to reproduce

  1. Install Haraka.
  2. partially customize helo.checks, such as 'cat "[reject]" >> config/helo.checks.ini
  3. establish a connection with an invalid hostname

Step #2 might not be necessary and/or relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant