Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • Sympl Sympl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sympl.iosympl.io
  • SymplSympl
  • Issues
  • #310
Closed
Open
Issue created Apr 08, 2021 by Paul Cammish@kelduumOwner

sympl-mail: config/antispam doesn't work as expected

What is expected to happen:

  • With the antispam file at /srv/example.com/config/antispam and empty, spam mail identified as spam should be rejected.

  • With the antispam file at /srv/example.com/config/antispam and containing tag, spam mail should:

  1. have the X-Spam-Status: spam header set, and the mail accepted.
  2. be delivered to the Spam mail folder of the user.

What actually happens is that 1 works as expected, but 2 rejects the mail as spam regardless of the tag setting, unless the config/antispam file is world-readable, which it likely shouldn't be.

In no instance (apparently inherited from Symbiosis) does the mail actually get placed in the users Spam folder, although it would be possible to create a sieve filter to do this, or for Dovecot to handle it, the mail is placed in the normal mail folder.

A quick fix would be to change /etc/exim4/sympl.d/10-acl/50-acl-check-rcpt/80-enable-antispam-check to:

${if match{${extract{smode}{${stat:VHOST_DIR/${domain}/VHOST_CONFIG_DIR/antispam}}}}{\Nr\N}{\

A fix for tagging spam properly would be to enable the subject rewrites by default, by adding the following to /etc/exim4/system_filter:

if $h_X-Spam-Status: contains "spam"
then
   headers add "Original-Subject: $h_subject"
   headers remove "Subject"
   headers add "Subject: *** SPAM *** $h_original-subject"
endif

Note this also affects config/antivirus, which has a similar (undocumented) tagging function for virus infected emails in /etc/exim4/sympl.d/10-acl/50-acl-check-rcpt/85-enable-antivirus-check.

Assignee
Assign to
Time tracking