Outlook-Like Rules engine

Open
#451 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

Start by reviewing issue #404 and the existing scheduled-job system. This issue proposes configurable rules with events, conditions, and actions, including tag cleanup and bulk processing of existing emails; done would require a defined scope and an agreed implementation plan for those capabilities.

Written by the indexing model from the issue text.

Description

feature-request

Microsoft Outlook (and other email clients) let you define rules that automatically take actions based on data like the sender's email, subject line and other properties at different events. You can also use these to bulk process existing emails.

For example, if an email is received with certain text in the subject line, it can be automatically replied to, moved to another folder, deleted, etc.

If a similar system existed in Hydrus, one way to accomplish the goals of #404 would be a rule like:

  • On a tag being added to a file in namespace motive
  • If any tags already exist for that file in namespace motive
  • Action prevent the change (or show a warning, etc.)

This could be another type of scheduled job to automate regular tag cleanup.

Dominant language
Python
Stars
3.2k
Forks
207
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hydrusnetwork/hydrus

All issues in hydrusnetwork/hydrus

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.