Re: The Maia 2.0 Wishlist/Brainstorming Thread
Bubba Brown <bubba-UmgsxY/[email protected]>
| Newsgroups | gmane.mail.virus.maiamailguard |
|---|---|
| Organization | Beers 2 u |
| Message-ID | <[email protected]> |
Great to hear from you, Robert, I'm jazzed to hear that you are brainstorming 2.0. Thoughts about the technologies used: Looking back at the parts of maia that have aged well, I'd have to include spamassassin itself, and all the perl parts in general. It's a thing of beauty to see how well it's stood the test of time. My concern with perl is that it has run out of steam. Python now has huge momentum, and in fact, there is a drop-in replacement for spamassassin written in python (orangeassassin) which works with spamassassin rule sets. So that's something to consider. (not to mention that in the informal benchmarks I've run, python 3 is now faster than perl) The most fragile pieces have proved to be php and pear. I wonder if the php API is settling down - if not, maybe we look at django or javascript or something? Database - mysql has worked very well for all of my maia setups, but I wonder if a document orietned database like mongodb might be a better fit for some or all of the functionality. Just a thought, maybe I'm way off base here. Big picture thoughts: One of the advantages the giants have is a global network that allows them to see aggregate patterns. It would be nice to leverage something like that. Things like DCC, razor etc are a step in the right direction, but could there be additional possibilities? I've found that spamassassin with a well trained Bayes db is a good spam detector, but even so, some spam gets through. The thing is, the junk filter in Thunderbird flags it 99% of the time. I wonder if we can look at that and see what can be borrowed. Best, Bubba On 4/14/20 12:31 PM, Robert LeBlanc wrote: > All right, let’s get the ball rolling on the next generation of Maia. I know it’s been talked about sporadically for years, but there’s nothing like a global pandemic to provide the motivation and the time to get things done—and clearly this puppy needs a from-the-ground-up redesign; it’s not 2003 anymore :) > > With that in mind, I figured I would start a brainstorming thread to collect some ideas from you about what you’d like to see in Maia 2.0. I certainly have a lot of ideas of my own about what I’d like to see in a next-gen product (and I’ve shared a lot of those ideas on this list over the years), but let’s start with a clean slate. > > As always, the cardinal rules of brainstorming apply: > > (1) There are no “bad" or “dumb” ideas—anything can be a spark for inspiration! > > (2) Don’t worry about whether an idea is “practical” or “feasible” at this stage; we’ll worry about the “how” part later. > > (3) Focus on high-level ideas, rather than low-level implementation details—the “what”, rather than the “how”. > > And so with that, I open the floor to your wish lists, your feedback about what you’d like to bring forward from Maia 1.x (and what you’d get rid of in a heartbeat!), and your “Product X has this cool feature I wish Maia had…” contributions. > > Let’s see what we can come up with—3…2…1…GO! :) > > > _______________________________________________ > Maia-users mailing list > [email protected] > http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users _______________________________________________ Maia-users mailing list [email protected] http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users