2
[Feature Request]Mail Rules Cannot Mark Messages as Read When No Document Is Created
Source: paperless-ngx/paperless-ngx#12902 · opened by @drz8gwzc6y-stack
Description Feature 1: Execute Actions Even When No Document Is Created Current behavior couples mail actions to successful document creation. Example: • Rule matches email • No attachment exists • No document created • Mark as Read action not executed Suggested behavior: Allow actions such as: • Mark as Read • Delete • Move • Archive to execute independently of whether a document was ultimately created. This would eliminate the need for duplicate mail-client rules. Feature 2: True Ignore Rules Many users receive emails that are useful for filtering but should never be archived as documents. Examples: • Bank transaction alerts • Marketing emails • Security notifications • Duplicate payment confirmations • Vendor-specific messages that are superseded by better receipts Suggested new rule action: Ignore Message Behavior: • Rule matches ̶…
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature Request] Append printed E-mail and/or attach e-mail body to PDF attachments
8 votes · 0 comments
[Feature Request] Allow greater control over password requirements
1 vote · 0 comments
[Feature Request] Improvements: Logging
6 votes · 0 comments
[Feature Request] Mail Rule: Add option for full-matching fields (esp. From for security)
3 votes · 0 comments
[Feature Request] Mail Rule: add "Delivered-To" filter
4 votes · 0 comments
No comments yet.