[DC-Users] Mail Revamping #2

DuckCorp Admin Team dc-admins at lists.duckcorp.org
Wed Jun 27 04:44:55 CEST 2018


=== Mail System Redundancy ===

Our old antispam system has been shutdown and Toushirou has been 
promoted to full MX1/MDA/MAA. This means we now have two machine 
receiving mails, filtering spam and synchronizing with each-other (SIEVE 
rules and antispam learning are synced too).

I just updated the DNS records so that 
{smtp,mail,imap,pop,sieve}.duckcorp.org now balance between the two. So 
if one machine is down, you should be able to retry to reach your mail 
on the second machine.

The webmail is currently not redundant but we're working on it.

The mailing-lists will stay on Orfeo as there is currently no way to 
make this service redundant.

=== Note about the Antispam ===

We had some user questions so I wanted to clarify a few things.

The new learning system is very similar to the previous one. The big 
change is: from now on all learning is shared between users. This means 
you benefits from SPAM caught by other users but it makes the learning 
less personalized. It is difficult to evaluate what's best but per-user 
learning made the system very complex and was very resource intensive so 
we decided to try the shared method. Many well known big companies also 
use shared training, so that new users don't start with a blank system 
which would need weeks or months to be well trained and it seems to work 
quite well.

Another important point is how to train the system. We simplified the 
old system and the new one does not have a web interface for users 
anyway. The 'Junk' folder (your mail client may translate the name) is 
used to collect discovered SPAM. If you move mails into it you inform 
the system it is a spam it should have caught. If you move a mail out of 
it then you inform the system it made a mistake and this is not a spam.

To get detected SPAM automatically put into the 'Junk' folder there is a 
default SIEVE filter. But if you added your own filters, then you need 
to include the default rule into your configuration as explained here:
This was done to allow users to override the default rule if they wanted 
another workflow.
We're wondering if this has any real application and thinking about 
making this rule compulsory (processed before any user filters). Your 
input on this matter is welcome.


Marc Dequènes (Duck)

More information about the DC-Users mailing list