To ensure that no email gets at least to user Junk folder use: This can be an issue if we are experimenting with SPAM scores.
2 Increasing trust of emails coming from my networks.1 Enable all SPAM to be delivered to junk folder.Similarly if some list is very good at catching spam perhaps increase its score from 2.0 to 4.0 or higher. If some blacklist is having too many customer contact addresses then we can reduce score from 2.0 to a much lower value, even 0.0 (Basically not using the list). Now over time we can adjust score of various blacklists to suit organization needs.X-Spam-Status: No, score=3.303 required=6.6 tests= autolearn=no autolearn_force=no where CUSTOM_LOOKUP_27, 50 and 62 are some of the blacklists that seem to have the sender server email ID in the blacklist. The headers should contain something similar to: After this send email from public server (eg gmail) to your server.After inserting the config restart services as zimbra user using:.Note creating sub-folder /opt/zimbra/conf/sa and creating custom. The config lines should be inserted in file ' /opt/zimbra/conf/salocal.cf.in' after existing header/describe/score rules.If you plan to use the recommended rbl list as it is then you can directly use #Recommended spamassasin configuration.
Example erlang escript that can take a list of domains and convert it to spamassassin config is captured at #Erlang script for conversion For any future rules we should use a different key such as CUSTOM_LOOKUP_2, CUSTOM_LOOKUP_3, etc. Header CUSTOM_LOOKUP eval:check_rbl('zen','.') describe CUSTOM_LOOKUP Entries listed in RBL score CUSTOM_LOOKUP 2.0 where CUSTOM_LOOKUP key in the three lines must match. Convert the list to spamassasin configuration format such as:.Create a list of blacklists to use for scoring, for example, there is a list at Recommended list is captured at #Recommended RBL List.If required use ' zmmtactl restart' after removing the MTA level client RBLs. Stop referring to any client RBLs at admin interface Configure -> Global Settings -> MTA.Thanksfully there is option in Zimbra to use client RBLs for scoring instead of rejecting complete email. They should only be used for scoring such that at most email goes to junk folder. If you look at blacklists such as they are clearly specify that they should not be used for direct rejection. Both these options are unmanageable in long run. This left option of either stopping to use that blacklist or adding the email server IP as part of trusted MyNetworks list. This created issue if any important contact's email server was in any blacklist. Traditionally any sender email IP was looked among various client RBLs and if found to be blacklisted, the email was rejected right away. Home > CentOS > CentOS 8.x > CentOS 8.x email servers > CentOS 8.x Zimbra > CentOS 8.x Zimbra Configure spamassasin email score based on client RBL
0 kommentar(er)
