Good morning Benny, the lints are done against a stock install with all the default modules. I agree it was an oversight that the v-bounce rules did not lint. There were both new and long-standing issues mixed in there as far as I could tell.
I've already committed a change for it and tested it. Now it has to go through the process for rule promotion and it will be published. So over the next few days you can try sa-update and the linting issue should be fixed. You can also manually download the bounce file from that commit and put it in your installed rules directory typically in /var/lib. Also, the KAM ruleset is available as a channel. Please see www.mcgrail.com for more information. There's a news article from November with more details and instructions on how to use it. Regards, KAM On Thu, Jan 7, 2021, 06:13 Benny Pedersen <[email protected]> wrote: > On 2021-01-07 03:28, Kevin A. McGrail wrote: > > > We use an automated process for the publishing of the KAM channel > > which includes linting it several times. > > the automatic does fail if all plugins is default enabled under test :=) > > > KAM Channel, I believe disables __MY_SERVERS_FOUND so if you have that > > and stock, the issue is hidden, but yes, vbounce would cause this > > issue. > > your commit still not resolve it > > > I found a similar endif parsing issue in the file and much of the file > > needs to be ifplugin checked and wasn't. > > time to make kam rules on sa-channel so atleast it lints > > > svn commit -m 'Added better plugin check for vbounce and vbounce > > ruleset' > > Sending rules/20_vbounce.cf > > Transmitting file data .done > > Committing transaction... > > Committed revision 1885222. > > one more time please >
