Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 587
    • Issues 587
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 48
    • Merge requests 48
  • 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
  • #6051
Closed
Open
Issue created Feb 07, 2021 by KoS@kos

Trigger junk move by Subject line impacts forwarded emails

The "Move Spam Emails to Junk folder" option creates a sieve filter line that targets the Subject line of the mail: if anyof (header :contains "X-Spam-Flag" "YES", header :contains "X-Spam" "Yes", header :contains "subject" "*** SPAM ***", header :contains "subject" "***SPAM***") (see https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/server/conf/sieve_filter.master#L10)

The problem with the subject line is, that if such an email (e.g. a false positive) is being forwarded to another user, it ends up again in the Junk folder, because the subject still matches the "*** SPAM ***", as long as the user didn't remove it manually.

I suggest to remove the subject check, but only rely on header lines added by rspamd (and spamassassin), e.g. by adding the check header :contains "X-Spam-Status" "yes" too.

Edited Feb 07, 2021 by KoS
Assignee
Assign to
Time tracking