starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 13:05:53 +03:00

[GH-ISSUE #679] Add a one-way convert to code option for existing options in the GUI | was: Review all Sieve actions, in all different use cases (Standalone or within Tiki, with or without Sieve) #441

New issue

Closed

opened 2026-02-25 21:35:02 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 21:35:02 +03:00

Owner

Originally created by @marclaporte on GitHub (Feb 24, 2023).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/679

Originally assigned to: @josaphatim on GitHub.

To @josaphatim (mostly)

We have different use cases:

Standalone Cypht
- with mailbox that doesn't support Sieve
- with mailbox that supports Sieve
Cypht in Tiki: https://doc.tiki.org/Email-filters
- with mailbox that doesn't support Sieve
- with mailbox that supports Sieve

@henrique-borba and I reviewed a few other webmail clients, and we covered a quite complete list of actions via the creation of a new lib: https://github.com/henrique-borba/php-sieve-manager

It is expected to be a little shaky at first. So please review all the use cases and all the actions and address any issues your encounter.

Sieve is a standard so in theory, it should behave exactly the same everywhere. But in practice, there can be some minor divergences. So please use Gandi as the reference.

As a reference: Here is original task: https://github.com/jasonmunro/cypht/issues/9

Originally created by @marclaporte on GitHub (Feb 24, 2023). Original GitHub issue: https://github.com/cypht-org/cypht/issues/679 Originally assigned to: @josaphatim on GitHub. To @josaphatim (mostly) We have different use cases: - Standalone Cypht - with mailbox that doesn't support Sieve - with mailbox that supports Sieve - Cypht in Tiki: https://doc.tiki.org/Email-filters - with mailbox that doesn't support Sieve - with mailbox that supports Sieve @henrique-borba and I reviewed a few other webmail clients, and we covered a quite complete list of actions via the creation of a new lib: https://github.com/henrique-borba/php-sieve-manager It is expected to be a little shaky at first. So please review all the use cases and all the actions and address any issues your encounter. [Sieve is a standard](https://en.wikipedia.org/wiki/Sieve_(mail_filtering_language)) so in theory, it should behave exactly the same everywhere. But in practice, there can be some minor divergences. So please use [Gandi](https://docs.gandi.net/en/gandimail/sieve/index.html) as the reference. As a reference: Here is original task: https://github.com/jasonmunro/cypht/issues/9 ![Sieve-and-similar-action-in-Cypht-and-Tiki](https://user-images.githubusercontent.com/1004261/221098713-f97d78f3-16e6-4560-964e-281fb630f0a2.png)

kerem closed this issue

2026-02-25 21:35:02 +03:00

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@marclaporte commented on GitHub (Feb 24, 2023):

This can give you ideas for the UI: http://code.uoa.gr/p/avelsieve/screenshots.php

@marclaporte commented on GitHub (Feb 24, 2023): This can give you ideas for the UI: http://code.uoa.gr/p/avelsieve/screenshots.php

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@dumblob commented on GitHub (Feb 24, 2023):

Yeah, avelsieve is crazy complicated (but seems really comprehensive). I think Cypht should stay with the "limited use case" approach.

Namely define precisely ~7 most common use cases for which templates/one-click filter setup/form should exist and then a "convert to code" button which would irreversibly bring you to a plain text editor (perhaps with syntax highlighting if that is your thing) where you would get real-time feedback (any errors/warnings taken directly from the backend Sieve engine with no changes to them unless security issues would arise in which case the relevant parts should be substituted with random data/anonymized and a separate note about this should be appended) from the server after each keystroke.

WDYT?

@dumblob commented on GitHub (Feb 24, 2023): Yeah, `avelsieve` is crazy complicated (but seems really comprehensive). I think Cypht should stay with the "limited use case" approach. Namely define precisely ~7 most common use cases for which templates/one-click filter setup/form should exist and then a "convert to code" button which would **irreversibly** bring you to a plain text editor (perhaps with syntax highlighting if that is your thing) where you would get real-time feedback (any errors/warnings taken directly from the backend Sieve engine with no changes to them unless security issues would arise in which case the relevant parts should be substituted with random data/anonymized and a separate note about this should be appended) from the server after each keystroke. WDYT?

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@marclaporte commented on GitHub (Feb 24, 2023):

@dumblob Good point: I think we forgot an option for manual entry.

@marclaporte commented on GitHub (Feb 24, 2023): @dumblob Good point: I think we forgot an option for manual entry.

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@marclaporte commented on GitHub (Mar 12, 2023):

Wait! We do have manual entry.

It's not "convert to code" but it should be good enough for people that need more than the GUI.

@marclaporte commented on GitHub (Mar 12, 2023): Wait! We do have manual entry. ![2023-03-12_163814](https://user-images.githubusercontent.com/1004261/224572429-2b97bead-0168-4aeb-a817-a6a02a0529fb.png) It's not "convert to code" but it should be good enough for people that need more than the GUI.

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@dumblob commented on GitHub (Mar 15, 2023):

Wait! We do have manual entry.

Yes, that is necessary.

It's not "convert to code" but it should be good enough for people that need more than the GUI.

The reason why I wrote "convert to code" is to have an easy (from a geeks perspective) way to see how the sieve filters are structured internally to have more freedom to interact with other sieve filters (refer to them, mimick them, etc.).

@dumblob commented on GitHub (Mar 15, 2023): > Wait! We do have manual entry. Yes, that is necessary. >It's not "convert to code" but it should be good enough for people that need more than the GUI. The reason why I wrote "convert to code" is to have an easy (from a geeks perspective) way to see how the sieve filters are structured internally to have more freedom to interact with other sieve filters (refer to them, mimick them, etc.).

kerem commented

2026-02-25 21:35:02 +03:00

Author

Owner

@marclaporte commented on GitHub (Dec 20, 2023):

@dumblob Done. Please test and re-open if further work is needed.

Thanks!

@marclaporte commented on GitHub (Dec 20, 2023): @dumblob Done. Please test and re-open if further work is needed. Thanks!

kerem referenced this issue

2026-02-25 21:36:18 +03:00

[PR #441] [MERGED] Add Archive action to lists (All Mail, Basic Search, Advanced Search, etc.) #814