On August 2, 2015 7:36:36 PM CEST, RW <rwmailli...@googlemail.com> wrote: > In future start with > > man spamassassin > > which will lead you to: > > CONFIGURATION > Mail::SpamAssassin::Conf SpamAssassin configuration files
I think I've actually seen this page rececntly. I also remember having looked through the bayes_* options (about a week ago) to see whether there's one that might indicate the number of required messages learnt, but couldn't find any (now I've seen bayes_min_ham_num / bayes_min_spam_num). I don't know how that happened, perhaps I was seeing another page (perhaps online), perhaps I had too many things in my mind then at the same time and was interrupted or unconcentrated (when starting to configure these systems (DNS, qmail, ezmlm, qpsmtpd, dovecot, SA), there are just too many things to take care of to not make errors sometimes). > Normally the main man page has the name of the project or its main > executable. It's not normal to document how a feature is configured > in the documentation for library that implements that feature. qpsmtpd is different here since it has a plugin architecture and then it definitely makes more sense to document things in the plugins, which are just modules. If spamassassin does not have such an architecture then I agree it makes sense to document options where they are processed, i.e. the module which parses them. I know I'm sometimes confusing spamassassin and qpsmtpd. Both are in Perl and used together in my setup. I've grown a habit to thinking "docs are in the modules" and when I was checking the SA docs again before sending my post I followed this habit without realizing that it's not the configuration of a qpsmtpd plugin in this case. Please don't judge me too hard, I'm trying to get on with things as quickly as I can like most everybody, I've got other things on my plate, too. So, I don't have a suggestion for improvement. Hopefully my post still helped the OP? Cheers, Christian.
