Author: Adam Language: text
Description: Spam list follow-up Timestamp: 2015-06-01 16:36:45 +0000
View raw paste Reply
  1. Hi folks
  2.  
  3. I had the same issue regarding GMail & other big senders as Chris who
  4. emailed you in the last episode.
  5.  
  6. I'll quote an entry from my blog which you covered a while back :)
  7.  
  8. "I found an amazing workaround with bgpd. bgpd(8) is a Border Gateway
  9. Protocol daemon whose job is to propagate routing tables with other
  10. systems, fortunately for me some smart folks decided to re-purpose it to
  11. distribute spamd(8) white-lists from large email servers. My puny little
  12. server had no chance to get a sane amount of traffic that would allow
  13. gmail.com to pass through, but grabbing the shared white-list made it
  14. almost guaranteed that legitimate email from GMail would go through
  15. without loosing the benefit provided by spamd itself. The alternative
  16. was to blindly white-list a large range of servers - I much prefer those
  17. that went through the trouble of grey-listing against a more popular
  18. exchange."
  19.  
  20.  
  21. To give you an idea on how that behaves.
  22. # 116 were not white listed in the bgpd list
  23. # spamdb | wc -l
  24.     116
  25. # out of that 115 past through the filters already
  26. # spamdb | grep GREY | wc -l
  27.       1
  28. # the system is up for 11 days and delivered 3929 emails
  29. # smtpctl monitor                                                        
  30. --- client ---  -- envelope --   ---- relay/delivery --- ------- misc
  31. -------
  32. curr conn disc  curr  enq  deq   ok tmpfail prmfail loop expire remove
  33. bounce
  34.   0 3944 3944     0 4017 4017 3929      89      88    0      0      0  
  35.     45
  36.  
  37. I love this method because I don't have to 'babysit' a whiltelist.
  38. Additionally since the bgpd distributed list is constructed from an
  39. actual spamdb installation - the servers go through the 'verification
  40. phase' that I installed spamd for, and they will drop out of it if they
  41. start misbehaving.
  42.  
  43. Those 116 hosts are mosty people running their own MX, so not generating
  44. enough of emails to go through the distributed spamd whitelist. Though
  45. they are not problematic as they don't use a server farm to deliver
  46. emails.
  47.  
  48. You can learn how to set it up on this page:
  49. http://bgp-spamd.net/index.html
  50.  
  51. Hope this helps Chris out :)
View raw paste Reply