Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 552
    • Issues 552
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4664
Closed
Open
Created May 25, 2017 by Ispcomm@ispcomm

Move to junk shall be last in dovecot .sieve recipe

The "Move to Junk" setting in mailbox settings creates a .sieve recipe at the beginning of the mail. This prevents user to add exception rules for whitelisting recipients or doing any other filter work, because filters are inserted after the Move to Junk rule.

It would probable be preferable to have the Move to Junk last in the .sieve so that the user can insert other rules that will modify the move-to-junk default.

There's a thread related to this issue here: https://www.howtoforge.com/community/threads/spamfilter-per-user-whitelist.76421/

This is an example of the currently created .sieve which illustrates the problem:

require ["fileinto", "regex", "vacation"];

if header :contains "X-Spam-Flag" "YES" { fileinto "Junk"; stop; }

if header :regex ["from"] ["^whitelisted@sender.org$"] { fileinto "INBOX"; stop; } keep;

Assignee
Assign to
Time tracking