https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6980
--- Comment #8 from AXB <[email protected]> --- (In reply to Kevin A. McGrail from comment #7) > (In reply to AXB from comment #6) > > (In reply to Kevin A. McGrail from comment #4) > > > (In reply to AXB from comment #3) > > > > I see good reasons for not adding a description to some rules. > > > > > > I consider it a bug. Are you referring to rules you don't want the black > > > hats to analyze or something where you hope the obscurity helps? > > > > if somebody has the knowledge to analize, it's ok. > > but there's a huge clueless mainsleaze market which screams for easy to > > understand descriptions. It's questionable how much help one is willling to > > offer. > > Understood. Then perhaps a description that at least says it isn't > documented on purpose as a compromise? > > "This description intentionally left blank." is fine with me but I want to > avoid laziness where description are missing that should exist. I'll stick to the highly intuitive options like describe AXB_OBFU_MULE spacey mules -- You are receiving this mail because: You are the assignee for the bug.
