| ||
Fri 2024-04-19
Thu 2024-04-18
Mon 2024-04-15
Butterick’s Practical Typography Sat 2024-04-13
Fri 2024-04-12
Wed 2024-04-10
Boy Meets Boy Meets Boys’ Love Tue 2024-04-09
Mon 2024-04-08
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
Did you know SpamAssassin sends
data offsite? I only noticed while debugging why spamassassin
sometimes takes a full minute to classify a message.
I'm having a hard time finding a full human-readable list of what it does, but if you have the source I think grep 'tflags.*net' rules/* gives you a dump. It at least does a bunch of DNS lookups and checks against Vipul's Razor, DCC, and Pyzor. I don't think SpamAssassin is evil. I am surprised that it does network checks by default. There's the obvious privacy issue. And network overhead can be high, particularly with 60 second timeouts. It seems like spamassassin installations are vulnerable to denial of service; if an attacker can cause all spamassassin installations to wait 60 seconds to classify every email, it could cause chaos in mail delivery. But network-based checks can be really useful. The DNS heuristics look great and the collaborative spam databases are a real solution to the spam problem. There's an obvious commercial opportunity here. For now I'm leaving network checks on. If you want, you can turn network checks off with the flag --local. |
|
