We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When adding an address such as: [email protected] in rcpt_to.routes.ini it fails to load it with error:
Invalid line in config file '/usr/local/haraka/config/rcpt_to.routes.ini'
This stems from haraka-config/lib/readers/ini.js which makes use of
module.exports = { section: /^\s*[\s*([^\]]?)\s]\s*$/, param: /^\s*([\w@:._-/[]]+)\s*(?:=\s*(.?)\s)?$/, comment: /^\s*[;#].$/, line: /^\s(.?)\s$/, blank: /^\s*$/, continuation: /\[ \t]*$/, is_integer: /^-?\d+$/, is_float: /^-?\d+.\d+$/, is_truth: /^(?:true|yes|ok|enabled|on|1)$/i, is_array: /(.+)[]$/, }
...
match = regex.param.exec(line) if (!match) { exports.logger(`Invalid line in config file '${name}': ${line}`) continue }
The param regex doesn't allow + signs. This can easily be changed, but will it break something else ?
The text was updated successfully, but these errors were encountered:
Presuming that you've also changed the qmail config to use + as the extension delimiter, I can't immediately think of anything else it would break.
Sorry, something went wrong.
No branches or pull requests
When adding an address such as: [email protected] in rcpt_to.routes.ini it fails to load it with error:
Invalid line in config file '/usr/local/haraka/config/rcpt_to.routes.ini'
This stems from haraka-config/lib/readers/ini.js which makes use of
module.exports = {
section: /^\s*[\s*([^\]]?)\s]\s*$/,
param: /^\s*([\w@:._-/[]]+)\s*(?:=\s*(.?)\s)?$/,
comment: /^\s*[;#].$/,
line: /^\s(.?)\s$/,
blank: /^\s*$/,
continuation: /\[ \t]*$/,
is_integer: /^-?\d+$/,
is_float: /^-?\d+.\d+$/,
is_truth: /^(?:true|yes|ok|enabled|on|1)$/i,
is_array: /(.+)[]$/,
}
...
The param regex doesn't allow + signs. This can easily be changed, but will it break something else ?
The text was updated successfully, but these errors were encountered: