Skip to content

Inbox Rules for Labels #8374

Open

Description

@wrdhub

When defining an inbox rule, i want to be able to select a label as a target, so that this label gets assigned to all matching emails.

Extend the inbox rules in a way that the user must specify a target folder (Inbox is a valid target) and the user can in addition assign one or multiple labels to the rule.

Need:

  • Gather more requirements

Activity

  1. JerryLerman commented on May 27, 2025

    @JerryLerman

    I was surprised that this wasn't implemented given the hoopla surrounding the label announcement. Of course, labels should be assigned based on inbox rules.

  2. hbunke commented on Jul 2, 2025

    @hbunke

    +1! This is one of the main advantages of labels

  3. hrb-hub commented on Sep 1, 2025

    @hrb-hub
    Contributor

    Just leaving this here for inspiration :)

    …It would be amazing to have more conditions like:
    Body/content contains
    Has attachments (yes/no)
    File extension (.pdf, .docx, etc.)
    File size or email size
    Sender domain (e.g., all emails from github.com)
    Sender is in address book
    And more actions such as:
    Add labels (my main request!)
    Auto-reply
    Forward
    Delete
    Mark as read/unread
    Enable/disable notifications
    Combine multiple actions
    Stop processing further rules…
    Source: https://old.reddit.com/r/tutanota/comments/1n4ri42/inbox_rules/

  4. thomrad commented on Oct 7, 2025

    @thomrad

    Absolutely needed! +1

  5. javigs commented on Oct 20, 2025

    @javigs

    Totally agree! +1

  6. Matcher6256 commented on Nov 25, 2025

    @Matcher6256

    Please add this feature ╯︿╰

  7. longstory0505 commented on Dec 5, 2025

    @longstory0505

    labels without inbox rules are kind of useless.

  8. added
    roadmaplabel to indicate that this issue is/was part of the roadmap and is visible on the website
    on Feb 9, 2026
  9. added this to the Roadmap milestone on Feb 9, 2026
  10. jomapp commented on Feb 24, 2026

    @jomapp
    Contributor

    some additional feedback from customers:

    • add multiple labels with a single inbox rule
    • add labels based on the mail body text
  11. jfhoop commented on Mar 5, 2026

    @jfhoop

    A must-have feature!

  12. hhopjh commented on Jun 4, 2026

    @hhopjh

    Mark as read/unread action is what I'm waiting for!

  13. thomrad commented on Jun 12, 2026

    @thomrad

    It would be very nice, if we can set more then one label and also filter for more then one label. At the moment, you can filter for more then one label, but with a logical OR - a logical AND would be very nice. I usually have more then one label, like company-bills or private-bills. So I can say, give me my private and bills label.

    Thank you!

  14. der-webtracker commented on Aug 18, 2026

    @der-webtracker

    I was just starting to De-Google my life and I would absolutely label the hell out of my mails if we get this feature for inbox rules. I would use it for example to have mails from different sources to a specific mail address being organised more deeply without going into more sub-folders. Pretty pretty please

  15. gammexane commented on Aug 22, 2026

    @gammexane

    I need this as well. +1

  16. wrdhub commented on Sep 18, 2026

    @wrdhub
    ContributorAuthor

    Issue for tracking greater Inbox Rule changes: #11201

  17. modified the milestones: Roadmap, on Oct 8, 2026
  18. linked a pull request that will close this issueDev mail inbox rule improvements #11680on Oct 19, 2026
  19. zoltansz commented on Nov 7, 2026

    @zoltansz

    It would be great to have the option to (i) match in the Condition according to Contacts (instead of individual emails only) so that even if their emails change, the Inbox rules remain valid, (ii) use in the conditions logical operators (AND, OR, NOT).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature: labelsimprovementnice-to-haves that are not impeding usage of any featuresroadmaplabel to indicate that this issue is/was part of the roadmap and is visible on the website

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂