Spam detection software, running on the system "avery.infomotions.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see eric_morgan_at_infomotions.com for details. Content preview: On Nov 15, 2016, at 1:34 PM, Karen Coyle <lists_at_KCOYLE.NET> wrote: > As for "safe from surveillance" etc., libraries are not miracle workers. Everything we do is in the real world. Given that the NSA captures every byte conveyed from point A to point B, how *could* libraries do anything about that? [...] Content analysis details: (-0.7 points, -1.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.6 URIBL_SBL Contains an URL's NS IP listed in the SBL blocklist [URIs: kcoyle.net] 0.1 URIBL_SBL_A Contains URL's A record listed in the SBL blocklist [URIs: kcoyle.net] 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_PASS SPF: sender matches SPF record -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
attached mail follows:
On Nov 15, 2016, at 1:34 PM, Karen Coyle <lists_at_KCOYLE.NET> wrote: > As for "safe from surveillance" etc., libraries are not miracle workers. Everything we do is in the real world. Given that the NSA captures every byte conveyed from point A to point B, how *could* libraries do anything about that? For starters, make sure that your website (and anything else you’re putting online) is served over a secure connection (https://, rather than just http://). Yes, encrypted traffic can be captured and encryption be broken, but it’s about making that too expensive to be done routinely, rather than making it impossible. Using a secure connection is about to become more important for very pragmatic reasons, as starting this January, Google’s Chrome (currently the most popular browser, by a wide margin) is going to begin explicitly warning users about non-HTTPS sites <https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html>. Ed -- Edward Almasy <ealmasy_at_scout.wisc.edu> Director • Internet Scout Research Group Computer Sciences Dept • U of Wisconsin - Madison 1210 W Dayton St • Madison WI 53706 608-262-6606 (voice) • 608-265-9296 (fax)Received on Wed Nov 16 2016 - 12:34:37 EST