In short:

How can incoming mails be assigned to proper Gemini projects by each incoming mail's "From" (without using dedicated Converse mailboxes or "magic" mail subjects)?

What would help probably as a first step would be an additional regex rule for "From" addresses for each mailbox in Converse, for example to realize a rule like "mails containing '(at)customer1.tld' must go into project 'Help Desk Customer1'". But I think this would require a prority mechanism for the different rules, too, because there may be a rule necessary like "mails from 'john(at)customer1.tld' go to 'Software Project 1'", because he is a key user of that product.

Or maybe there is already a plug-in interface in Converse, where we could hook into a (rather simple) self made dispatcher, as it was announced for MailboxPro?

In detail:

I'm testing Converse currently and need to know how the assignment process of incoming mails to their proper project/component could be improved.

We manage several projects in Gemini's terms: some projects that reflect our real software development projects (products) and some projects that are dedicated to key customers (meerely to use it for help desk affairs). We want to handle all incoming and outgoing support/issue mails through Converse to have all conversations added to their proper issue/task item as comment - that's what Converse is meant for, right? ;)

But: I want to have each item in its proper project (or "help desk project"), but I cannot teach our customers to mail issues to certain (eventually several) dedicated mail addresses, so every user/customer mails any issue or request to the same mail address - lets say to "support(at)worst-developers.ever" ;) What we also don't want to ask our users for is to enter some "magic" keywords into the mail's subject, because they won't do it right.

So how may I distribute all different mails into their proper project? I need to put it into its proper project right on arrival, because if I set up a "general incoming project" and move a generated item to its proper project later, future mails won't match for that issue/item, because the "item tag" in the notification mails' subjects don't match any more; the project tag of the moved item changes - although item number stays the same - and Converse does not find/know the former ID of this item, so a new item will be generated for the follow up mail.

What is meant with "Intelligent 'From' Email Address Management" in the product description? Is this only related to outgoing mails or did I miss something?