Comments you submit will be routed for moderation. If you have an account, please log in first.

Changes between Initial Version and Version 1 of Ticket #368, comment 12

Jan 12, 2013, 9:51:25 PM (2 years ago)


  • Ticket #368, comment 12

    initial v1  
    15151. spamassassin+spamass: the most efficient way to prevent tons of SPAM to be accepted. However, spamassassin have to be tunes itself to carry a global autowhitelist and bayes filter throught all user accounts. In adding pyzor, razor and ddc should be enabled with spamassasin.
    16 2. DNS blacking: the second most efficient way to block SPAM as these blacklists are well maintained.
     162. DNS blacklisting: the second most efficient way to block SPAM as these blacklists are well maintained.
    17173. DKIM/SPF signing: to reduce the probability that mails from your domain will be flagged as SPAM themselves it is a good idea to implement DKIM and SPF mechanisms in you domain. Many SPAM engines are considering DKIM/SPF setups today and will consider valid DKIM/SPF mails to be flagged as Ham.
    18184. while greylisting was very efficient years ago (> 5 years) most of the SPAMers have already adapted they engines by today.  Was also using greylisting in the beginning but nowaday itis not really efficient anymore and just delays your transfers. There are numeros webpages talking about this fact already. In my setup I replaced greylisting with DNS blacklisting and ended up with higher SPAM recognition rates and less false-positives.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Andreas Schwarz(Reporter, Participant)