Re: The Maia 2.0 Wishlist/Brainstorming Thread

Yes, addressing the “auto-confirm” thresholds in process-quarantine.pl was just a kludge—a quick and easy way to add a much-requested feature without having to redesign a big chunk of code.  I agree that it should be part of each user’s individual settings.

As for the whitelist/blacklist maintenance, you’re asking for a toggle that would switch everything from white to black (and vice-versa)?

> On Apr 14, 2020, at 7:19 PM, Lawrence Mulder <lmulder-iL7gtBVyNKCGUxFv0Br65wC/[email protected]> wrote:
> 
> Robert,
> 
> Thank you for your reply and for bringing your expertise back to the fore.
> 
> I guess that helps on number 3 but sounds like it could be done more flexibly such as per user in a new Maia?
> 
> Also on number 4 - you are correct about spam lists, I was thinking about the whitelist/blacklist maintenance.
> 
> Cheers.
> -Larry
> 
> ________________________________________________
> 
> Lawrence R. Mulder / RHCE, VTSP, SEC+
> Vice President, InformAbility, Inc.
> IT Consulting – On-Premise Systems - Cloud Systems
> lmulder-iL7gtBVyNKCGUxFv0Br65wC/[email protected] <mailto:lmulder-iL7gtBVyNKCGUxFv0Br65wC/[email protected]>
> http://www.informability.com/about <http://www.informability.com/about>
> https://www.facebook.com/informability <https://www.facebook.com/informability>
> Ph: 630-532-5941 <tel:6305325941>
> Fx: 630-532-5955 <tel:6305325955>
> ________________________________________________
> 
> From: [email protected]
> Sent: April 14, 2020 9:11 PM
> To: lmulder-iL7gtBVyNKCGUxFv0Br65wC/[email protected]
> Cc: [email protected]
> Subject: Re: [Maia-users] The Maia 2.0 Wishlist/Brainstorming Thread
> 
> Thanks Larry!
> 
> Just a couple of notes about (3) and (4), which are already in Maia 1.x.
> 
> For (3), I remember we added “auto-confirm” thresholds for spam and ham at one point, but it wasn’t configurable from the web interface, it had to be configured (globally) in the configuration file for the process-quarantine.pl script (i.e. /etc/maia/maia.conf).  For instance:
> 
> # If Bayes training is enabled, automatically learn items
> # with extreme scores, even without user confirmation.
> # Set these values conservatively, or undef to disable.
> 
> $autolearn_ham_threshold = -5;
> $autolearn_spam_threshold = 10;
> $autoreport_spam_threshold = 15;
> 
> As for (4), you can set all of the items on a given page to spam, non-spam, or delete just by selecting the column header.
> 
>> 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.
> 
> _______________________________________________
> Maia-users mailing list
> [email protected] <mailto:[email protected]>
> http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users <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

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSBR6OyClV7nkt4Wjkaao4RHY0d7AUCXpZ0rwAKCRAaao4RHY0d
7MQhAJ4gZ8YvwGKaDCMtK6uAzn5SBMf8OQCfTGDm3Lh2xeHjJjdzzQVWBjGwDMI=
=qrHc
-----END PGP SIGNATURE-----