Re: The Maia 2.0 Wishlist/Brainstorming Thread

Lawrence Mulder <lmulder-iL7gtBVyNKCGUxFv0Br65wC/[email protected]>
Newsgroups gmane.mail.virus.maiamailguard
Message-ID <DM5PR0501MB37525B589AEF24D4541C9182ADDA0@DM5PR0501MB3752.namprd05.prod.outlook.com>
Here are some items I have gleaned from using Maia for the past 15 years or so... in no particular order.

1. Some business or customers I lost to "the bigger guys" were because Maia lacked the ability to cache all email and act as a webmail client if the customer's own email system or internet link to their email system was down temporarily.  This doesn't make a lot of sense to me, but its what people think they need sometimes. 😊

2. Along these lines, it would be nice to be able to cache all email, even items that are whitelisted so that they can be re-delivered to the end user in case high level spam filtering or LUA's erroneously discard valid email.  My current install of maia does NOT cache whitelisted emails unless I am missing something.

3. On the web interface, It would be nice to have the system "auto-process" messages above or below a certain score threshold.  Rarely would a "suspected spam" message with a score of 40 really need me to "rescue" it from spam.  So, if I could tell maia to auto process messages that were above a 15 (or whatever number works for my message patterns), it would make the volume of spam I had to look at and confirm via the website much lower.

4. Also on the web interface, it would be helpful to allow the ability to toggle the status of every page of emails to a different status instead of having to change each message from spam to ham and vice versa.  It doesn't happen that often, but if there is a misconfiguration or for some reason Maia quarantines a bunch of emails, being able to toggle all 'suspected SPAM' to "non-spam" all at once would be very helpful.

5.  Whitelist/Blacklist management could be more robust also.  Using an AJAX'y type filter and a select all system to remove random email addy's that have been added to a user's whitelist would be super helpful.

6.  An option to prevent the '@' "user" due to spoofing or whatever, from being whitelisted which can cause a user's spam volume getting through to their inbox to jump way up.

7. Ability to set the time of day for a user to receive their quarantine digest (taking into account their timezone vs the one the server is in) instead of relying on an interval and a cron job would be great which doesn't take the end users' timezone into account.

8. Perhaps the ability to split a secondary email address off of an account from one user without having to delete the email address and corresponding messages to assign it to a different primary user?

9.  Incorporate the configuration of the protection level settings into the web interface instead of residing in the config.php file

10. Other config options from the /etc/maia.conf could be moved to the GUI?


Thanks,
-Larry

-----Original Message-----
From: Maia-users <[email protected]> On Behalf Of Robert LeBlanc
Sent: Tuesday, April 14, 2020 2:31 PM
To: Maia-Users Mailing List <[email protected]>
Subject: [Maia-users] The Maia 2.0 Wishlist/Brainstorming Thread

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.