Local Sieve: execution engine, sieve_processed flag, and retroactive run #101

Closed
opened 2026-05-15 16:34:07 +00:00 by guettlibot · 0 comments
guettlibot commented 2026-05-15 16:34:07 +00:00 (Migrated from codeberg.org)

Follow-up from #90 (local email filters UI). The UI for local Sieve scripts is now in place (schema, CRUD, routes, banners). The following pieces remain:

#117 - Transpilation to an Intermediate Rule-List / AST READY - guettli/sharedinbox - Codeberg.org

2. sieve_processed boolean on emails

Issue #90 answer (Q4): add a sieve_processed column to the local DB to prevent loop processing. Needs a schema migration and integration with the sync loop so new messages get filtered after download.

3. Retroactive 'Run on all inbox'

Issue #90 answer (Q6): include retroactive processing. Needs a UI entry point and a background task that applies active local scripts to all unprocessed inbox messages.

Follow-up from #90 (local email filters UI). The UI for local Sieve scripts is now in place (schema, CRUD, routes, banners). The following pieces remain: [#117 - Transpilation to an Intermediate Rule-List / AST READY - guettli/sharedinbox - Codeberg.org](https://codeberg.org/guettli/sharedinbox/issues/117) ## 2. sieve_processed boolean on emails Issue #90 answer (Q4): add a sieve_processed column to the local DB to prevent loop processing. Needs a schema migration and integration with the sync loop so new messages get filtered after download. ## 3. Retroactive 'Run on all inbox' Issue #90 answer (Q6): include retroactive processing. Needs a UI entry point and a background task that applies active local scripts to all unprocessed inbox messages.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: guettli/sharedinbox#101