Understood but the warnings can only be handled if we fork the development for internal and external. We have no plans to expend resources to do that so recommend you ignore the warnings. In fact, if you are seeing them in cron, you can safely take the debug out of your cron job and the warnings go away. Just run a --lint which will be silent without errors. NOTE: We don't publish it it fails lint so you really don't have to do that either but since you could be using a different version of SA or a plugin / if version error might creep up so good to lint. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Wed, Feb 12, 2020 at 8:17 PM Rick Gutierrez <xserverli...@gmail.com> wrote: > El mié., 12 feb. 2020 a las 16:28, Kevin A. McGrail > (<kmcgr...@apache.org>) escribió: > > > > Those are warnings to be expected as we develop the rules for our > internal use but share them free to the world. We encapsulate some rules > only useful in our environment and it can cause some noise if you look at > debug warnings. > > -- > > I send you this data, since I have a cron that downloads the file > every three days, and if I make the modification it will be > overwritten. > > > > -- > rickygm > > http://gnuforever.homelinux.com >
