Configurable custom actions (buttons)

[marclaporte]

Cypht has standard actions (delete, archive, etc.). Let's take this up a notch.

I do the same actions again and again. It would be nice to configure these actions. A bit like macros.

Part of the logic for filters: https://github.com/jasonmunro/cypht/issues/9 but manual trigger of actions.

Ex.:

• move email to a folder XYZ in another account
• forward to ABC and delete
• forward to DEF and archive

Thanks!

[dumblob]

@marclaporte you mean something like a button run now next to each filter chain?

[marclaporte]

@dumblob: yes, that as well. Any set of actions really.

[dumblob]

@marclaporte hm, I mean, having a button run now next to each filter is very easy to implement, but if there are any other actions (which? I think there do not exist any other meaningful actions except for sending emails), it'd get more complicated to implement.

[marclaporte]

Maybe I am misunderstanding. Can you elaborate on "filter chain"?

"which?": This is a long term goal: Parse emails for structured data and move to a database (http://doc.tiki.org/Trackers). Imagine invoices by email that are added to the accounting system.

I would like a button to bounce an email back to sender, simulating a non existant account.

Some more ideas here: http://james.apache.org/mailet/standard/mailet-report.html

For the short term, I want buttons like "move to accounting inbox", "move to accounting archive"

[marclaporte]

Also, one of our goals is to support the use case of generic mailboxes like info@, support@, accountspayable@, etc. Please see: http://doc.tiki.org/Groupmail

Actions could be:

• Add a threaded discussion about this email to coordinate on how to handle/reply.
• Convert to a task

I realize a lot of this will go beyond the use case of standalone Cypht. Configurable buttons could have 10 possible actions in standalone and 20 when embedded within an app like Tiki. And sooner or later, other web apps will follow our footsteps for JMAP and programmable emails!

[dumblob]

@marclaporte now I see what you mean. IMHO that has not much to do with Cypht, but rather with modules which Cypht already supports. Cypht itself has no need for such actions - they don't exist now, so there is no need for any buttons/... (i.e. no user interface).

But of course, you're free to write your own extension modules for Cypht and you'll get your buttons in the UI as well.

I doubt there is anything important to do in this front - Cypht is already quite extensible, so a generic support for "custom actions" is already baked in. You just need to get it moving by writing your very own modules (as the actions you mentioned are extremely specific and such module is IMHO not suited for inclusion in this repository).

Btw. "filter chains" is the "expected" outcome of https://github.com/jasonmunro/cypht/issues/9#issuecomment-623271697 - and my proposal here was to add one more button to trigger them manually in addition to triggering them automatically as soon as the user logs in and Cypht starts fetching new emails.