http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5213
------- Additional Comments From [EMAIL PROTECTED] 2006-11-29 11:55 ------- (In reply to comment #4) > Hipefully you'll agree that's not a very good situation. "Read the source" is > not exactly a good answer for any documentation, and even less so for standard > user-settable configuration options. Maybe that is a given, but the point of contention is 'Is spamassassin well documented?' Yes, it is, via perldoc. Spamassassin is an open source project, which is open to user contributions. Those contributions are not limited to the inner workings (read: source code), contributions to the documentation and wiki pages are more than gratefully accepted. If we aren't satisfied with the current state of affairs we have 2 options: 1) Complain about it, 2) get involved and be a part of the solution. Which a person decides to do is their choice but the latter of the two will definitely make more friends and increase the karma of the project as a whole. (In reply to comment #4) > (In reply to comment #2) > > The best source of documentation for the rules are the .cf files themselves. > > Hipefully you'll agree that's not a very good situation. "Read the source" is > not exactly a good answer for any documentation, and even less so for standard > user-settable configuration options. > > ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
