From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ewsd; Thu Jan 10 11:23:03 EST 2019 Received: (qmail 70457 invoked by uid 1001); 10 Jan 2019 08:22:57 -0800 Date: Thu, 10 Jan 2019 08:22:57 -0800 From: Kurt H Maier To: 9front@9front.org Subject: Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes Message-ID: <20190110162257.GC87615@wopr> Mail-Followup-To: 9front@9front.org References: <5BDAB1A586F7214BF811C877C6236247@wopr.sciops.net> <3A2CFA2F-1481-4AAB-BBD7-2693BE571394@stanleylieber.com> <1547132554.2306310.1630949240.274FBE6E@webmail.messagingengine.com> <3E5E5D37-1389-46B0-8C7C-92CD7FC635BE@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3E5E5D37-1389-46B0-8C7C-92CD7FC635BE@stanleylieber.com> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: agile firewall database lifecycle property controller On Thu, Jan 10, 2019 at 10:11:30AM -0500, Stanley Lieber wrote: > > i think all of this happened before qwx’s original message ever made it to the 9front mailing list server. This is correct. The spam flagging was my machine, and this was my fault because I didn't tell qwx that all messages coming in on port 25 (as opposed to 465) are scanned. Because this message was sent from a normal residential address, it set off all kinds of weird-ass alarms. Sorry for the noise, folks. khm