Hi, I've cross checked code, usage() and man pages for all options (command line and greylist.conf), and after these changes everything should be consistent: In greylist.conf.5, line 289, the "verbose" option (enable debug output) is mentioned to be equivalent to -d, while it is really -v which enables debug output. Additionally, the "lazyaw" option is missing from the greylist.conf man page. Other ideas: The -l command line option (enable debug in acl code) to milter-greylist doesn't have an equivalent option for greylist.conf - I guess it would make sense to add this. Could be useful to enable acl debugging on the fly, and the only other command line options without equivalent greylist.conf options are -c, -f configfile, -h, and -r (greylist.conf options for those wouldn't make sense). Is there anybody running milter-greylist without a greylist.conf ? One could argue that it makes sense to remove all but those 4 command line options completely, and leave configuration to greylist.conf. It's cleaner to update the configuration file than the startup file to modify milter-greylist behaviour, and the documentation would become more straight-forward. Opinions, anyone ? mp.
Message
configuration options
2005-05-25 by Martin Paul
Attachments
- No local attachments were found for this message.