How can I treat mail with a specific subject line as spam using Warden?

Using the WhitelistSubject/WelcomeListSubject Plugin

The simplest way to treat a specific subject as spam is to use the WhitelistSubject/WelcomeListSubject plugin as it also supports blacklisting.

  1. Navigate to Warden -> Settings -> Plugins Settings -> WhitelistSubject/WelcomeListSubject.
  2. Enter the subject line under Blacklist/Blocklist subject.
  3. Click the Update button to save your settings.
  4. Now any subject lines matching your entry will get a 100+ score applied to them.

WhitelistSubject/WelcomeListSubject

By Using a Custom Rule

If need more advanced rule you can add a custom rule to match the subject line.

  1. Navigate to Warden -> Rules -> Click on Add to add a custom rule.
  2. Select the Template select list and select the Header - Subject - Matches - Word template. More information about rules can be found here.
  3. Enter the name of the rule you want to add name field ( names must be less than 22 chars) and the new score you want to use in the score field (use 100 if you want it to be treated as spam).
  4. Click the Update button to save your settings.

Custom Rule

  • subject
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How can I change the interface language of the extension?

You can change the interface language under Settings -> Application Settings -> Locale...

How can I disable admin email notifications in Amavis?

Amavis has different default options for controlling where virus, spam, banned file attachments,...

How can I whitelist or blacklist a mail server from greylisting?

To Whitelist a Mail Server From Greylisting Navigate to Warden -> Settings ->...

How can I enable third party anti-virus signatures within Warden to improve the ClamAV detection rate?

Warden supports enabling third party anti-virus signatures to improve the detection rate. These...

How can I setup a local caching DNS resolver to speed up DNS queries used by Amavis?

Run the following command to check if local DNS caching is enabled: host -tTXT...