Re: The Maia 2.0 Wishlist/Brainstorming Thread
Robert LeBlanc <[email protected]>
| Newsgroups | gmane.mail.virus.maiamailguard |
|---|---|
| Message-ID | <[email protected]> |
I can see already that this thread is about to expose some details about Maia 1.x that many were not aware of :) This issue with whitelists/blacklists of one-time mailing list addresses, for instance, has always been solvable with the use of wildcards, it just hasn’t been an automatic process. For instance, suppose the one-time address looks like: reply-fe9316737162017971-58_HTML-122602019-7000612-2706-t3cJEeYdo10pzj28eHfH/[email protected] If you look at at least two of those emails, you’ll likely see that not all of that is random. Typically there’s a random portion and a fixed portion that identifies the subscriber (and possibly delivery options for that subscriber, e.g. HTML rather than plaintext). Maybe the second email has a reply-to of: reply-01d46100aa12018b09-12_HTML-122602019-7000612-2706-t3cJEeYdo10pzj28eHfH/[email protected] Comparing the two addresses, you might see that only the first portion is random, so you could use a whitelist rule like: reply-*_HTML-122602019-7000612-2706-t3cJEeYdo10pzj28eHfH/[email protected] It’s a pain that it has to be done manually, but it’s something that might be possible to automate if at least two samples are available. All that’s needed is to identify the variable portions and the invariant portions. Depending on your version of Maia 1.x, I remember we made a change at one point to have whitelists and blacklists apply to both the reply-to: and from: addresses, so your whitelisting of health-t3cJEeYdo10pzj28eHfH/[email protected] should work, too. Now I’m wondering if subsequent maintainers might have taken that out of the codebase? Anyhow, keep the ideas coming—these are really useful! :) > On Apr 14, 2020, at 4:52 PM, jjs - mainphrame <[email protected]> wrote: > > I see there have been some good replies. > > Just one pet peeve here. I want to be able to whitelist a particular sender address, say health-t3cJEeYdo10pzj28eHfH/[email protected] <mailto:health-t3cJEeYdo10pzj28eHfH/[email protected]>. So I click on "whitelist", but find that they end up in spam again. So I look in my whitelist and instead of health-t3cJEeYdo10pzj28eHfH/[email protected] <mailto:health-t3cJEeYdo10pzj28eHfH/[email protected]>, there is a one time throwaway address like "reply-fe9316737162017971-58_HTML-122602019-7000612-2706-t3cJEeYdo10pzj28eHfH/[email protected] <mailto:reply-fe9316737162017971-58_HTML-122602019-7000612-2706@messages.webmd.com>". If I've clicked on whitelist a lot, there will be a lot of different one time addresses in the whitelist. > > So, what I really want is to whitelist the visible sender address, regardless of whether it's vulnerable to spoofing. > > Whitelisting a one time address does me no good. > > jake > > > > On Tue, Apr 14, 2020 at 12:31 PM Robert LeBlanc <[email protected] <mailto:[email protected]>> 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] <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 _______________________________________________ Maia-users mailing list [email protected] http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSBR6OyClV7nkt4Wjkaao4RHY0d7AUCXpZnnAAKCRAaao4RHY0d 7BGSAKCCjxEN2EmMYXhWbO1ATA/COy8HFACfaPObfOnJauP6R3VqMwXKm32zR6g= =ADkh -----END PGP SIGNATURE-----