Topic: Subject contains [SPAM] after update to iRedMail EE 1.7.0
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): iRedMail EE 1.7.0
- Deployed with iRedMail Easy or the downloadable installer? EE installer / updater
- Linux/BSD distribution name and version: AlmaLinux release 9.7 (Moss Jungle Cat)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL (mariadb)
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? EE
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
After update to 1.7.0 the tag [SPAM] is added to (apparently all) email messages sent using this server as a relay. This happens also when the relevant flag is off (Spam Policy - Prefix text [SPAM] to the subject of spam).
Modifying this flag does nothing to /etc/amavisd/amavisd.conf and this is the diff from the latest file version before the update:
# diff -u amavisd.conf.20260326-210112~ amavisd.conf
--- amavisd.conf.20260326-210112~ 2026-03-26 21:01:12.070970083 +0100
+++ amavisd.conf 2026-03-26 21:01:12.074969993 +0100
@@ -156,8 +156,8 @@
$MAX_EXPANSION_QUOTA = 500*1024*1024; # bytes (default undef, not enforced)
# Prepend '[SPAM] ' to subject of spam message.
-$sa_spam_modifies_subj = 1;
-$sa_spam_subject_tag = '';
+$sa_spam_modifies_subj = 0;
+$sa_spam_subject_tag = '[SPAM]';
$defang_virus = 1; # MIME-wrap passed infected mail
$defang_banned = 0; # MIME-wrap passed mail containing banned name
I will try to restore the previous configuration file, but I suspect that it will be overwritten in subsequent updates.
What is the right way to fix this issue?
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.