Some brief history, in case there are developers who weren't working on Spambayes 5 years ago ;-):
I wrote the first crummy integration between Outlook and Spambayes, which worked really well (thanks to Tim), and was so ugly that Mark was inspired to replace it with something cool. After letting Mark do the heavy lifting, I eventually built a commercial product (InBoxer Antispam) which used Spambayes at the core, 'specially Marks integration code. Fast forward, oh, several years. InBoxer has customers who insist on using the product even though we've tried to kill it. Twice. And Outlook 2010 incompatibility is driving them nuts. I can't even tell them to go try Spambayes, because the same issues exist there. I have the following propositions, just to see if anyone is excited, err interested, or even unemployed. 1) We could contract with someone with experience to do the 2010 changes to the common code base, and then port those changes in our product. Payment to be negotiated, common code base changes freely usable in Spambayes. BTW, Mark H. is oversubscribed. Tried that. 2) We can offer a 1K prize to the developer submitting a patch/rev to the common code base that solves the problem to the satisfaction of the development lead (?Skip?) 2a) We could offer the the equivalent cash as a donation to the PSF if there is more interest. If there is any interest, please contact me directly as well as the list. -- Sean Sean True se...@inboxer.com CTO Inboxer @ Safecore, Inc **<https://clients4.google.com/voice/embed/webCallButton?id=0470b068193dc5360149c3504aa5d27df2ed9918>
_______________________________________________ spambayes-dev mailing list spambayes-dev@python.org http://mail.python.org/mailman/listinfo/spambayes-dev
