Generally, patches which "make sense" (whatever that might mean) to a wide audience I'll try and include in future releases. Some stuff (like local rules, etc) won't necessarily make it in. ORBS checks have just now been disabled in CVS.
C On Fri, 2002-03-22 at 00:50, Kenneth Chen wrote: > Hey all: > > I've seen a large amount of code and patches come through this mailing > list that enhance the performance of SpamAssassin. However, I'm no perl > guru (or any other language) so I'm not sure what I'd do with all those > snippets of code. > > Is it safe to assume that the code that proves reliable and useful will > eventually make its way into a release version of SpamAssassin, for those > of us that are not sophisticated enough to patch our own installations? > > For example, I saw someone mention that they commented out the ORBZ check > since it went offline; I wouldn't even know where to begin to do that, but > that seems like a reasonable 'update' to SpamAssassin so I would hope to > see that check commented out in a future release. > > Regards, > Kenneth > > > ----------------------------------- > Kenneth Chen > Unit Supervisor, Clark Kerr and UVA > Residential Computing > University of California, Berkeley > [EMAIL PROTECTED] > > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
