Config exim.conf for DirectAdmin
He spammed me from all left and right servers.
I decided to poke a little over the config exima. The shamanism brought to the fact that the staff config was completely reworked, a small selective greylisting and a dspam filter, as well as black and white lists were bolted.
He completely refused from spamassasin (in favor of dspam, which will be described in a separate article), because he eats memory not weakly, especially when the incoming mail shaft goes, and its efficiency suffers a little.
After shamanism, spam dropped by almost 80-90%. The rest goes through greylisting and then dspam.
The principle of filtration is as follows.
At the connect stage, all dynamic networks such as * .pool. * * .Dsl. * * .Dialup. * Etc. are dropped. (well, from where there will be a normal mailer?)
Then all hosts with incorrect / unregistered HELO are dropped
In check_recipient, drop hosts that are blacklisted. There is also a check for the presence of a reverse zone, the registered hostname and the presence of this host in the RBL lists. And the mail from these is not dropping, and sent to the greylist.
The greylist also leaves those hosts who decide to log in via smtp instead of esmtp.
Solved the problem (seemingly) with backscatterer.org (for what this is - see on their website) and spamming through bounce (otlups)
Especially I will not paint, the config is attached. Black list too.
')
When writing a config, information from exim.org.ua, mta.org.ua and lissyara.su was used.
If someone suddenly stumbles and uses it, I’m not responsible for the consequences.
Use at your own risk.
However, I will welcome any comments, additions and changes.
Files:
ps : The article is not mine, but of my friend SP999-UANIC, the administrator of hosting fs-host.net . If you like someone you can share an invite with him;)
UPD: SP999: but not necessarily under directadmin. use the mechanisms that are present in the config is possible for any eksima.
I decided to poke a little over the config exima. The shamanism brought to the fact that the staff config was completely reworked, a small selective greylisting and a dspam filter, as well as black and white lists were bolted.
He completely refused from spamassasin (in favor of dspam, which will be described in a separate article), because he eats memory not weakly, especially when the incoming mail shaft goes, and its efficiency suffers a little.
After shamanism, spam dropped by almost 80-90%. The rest goes through greylisting and then dspam.
The principle of filtration is as follows.
At the connect stage, all dynamic networks such as * .pool. * * .Dsl. * * .Dialup. * Etc. are dropped. (well, from where there will be a normal mailer?)
Then all hosts with incorrect / unregistered HELO are dropped
In check_recipient, drop hosts that are blacklisted. There is also a check for the presence of a reverse zone, the registered hostname and the presence of this host in the RBL lists. And the mail from these is not dropping, and sent to the greylist.
The greylist also leaves those hosts who decide to log in via smtp instead of esmtp.
Solved the problem (seemingly) with backscatterer.org (for what this is - see on their website) and spamming through bounce (otlups)
Especially I will not paint, the config is attached. Black list too.
')
When writing a config, information from exim.org.ua, mta.org.ua and lissyara.su was used.
If someone suddenly stumbles and uses it, I’m not responsible for the consequences.
Use at your own risk.
However, I will welcome any comments, additions and changes.
Files:
ps : The article is not mine, but of my friend SP999-UANIC, the administrator of hosting fs-host.net . If you like someone you can share an invite with him;)
UPD: SP999: but not necessarily under directadmin. use the mechanisms that are present in the config is possible for any eksima.
Source: https://habr.com/ru/post/84968/
All Articles