Runberg wrote:2) Potential spam should be moved to Junk folder (is this the guide to follow: https://docs.iredmail.org/move.detected … older.html )
yes.
I followed the guide, but even it is a fresh installation of iRedMail this setting already seemed to be added? - is it default in latest version?
Runberg wrote:3) Users should be able to mark spam for future reference (is this the guide to follow: https://docs.iredmail.org/store.spamass … n.sql.html )
yes.
I tried to follow the guide, but when updating the database I get this error:
mysql> USE sa_bayes;
Database changed
mysql> SOURCE /root/bayes_mysql.sql;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 5
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 5
ERROR 1146 (42S02): Table 'sa_bayes.bayes_global_vars' doesn't exist
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 6
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 9
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM' at line 14
mysql>Any good ideas?
1) Obvious spam should be deleted
2) Potential spam should be moved to Junk folder
So my idea is that obvious mail should just be deleted, but potential (when in doubt) spam should be moved to the junk folder. I assume the last part is in place now, but what about the first part - deleting obvious spam?
Are these the parameters to "play" with in /etc/amavis/conf.d/50-user
$sa_tag_level_deflt = 2.0; # add spam info headers if at, or above that level
$sa_tag2_level_deflt = 6.2; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 6.9; # triggers spam evasive actions (e.g. blocks mail)
$sa_dsn_cutoff_level = 10; # spam level beyond which a DSN is not sent
$sa_crediblefrom_dsn_cutoff_level = 18; # likewise, but for a likely valid From
#$sa_quarantine_cutoff_level = 25; # spam level beyond which quarantine is offAnd thanks for the link regarding the fourth idea - I think it will start working on that when everything else is in place 
