[SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[qwx]

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]

Spam detection software, running on the system "wopr.sciops.net",
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
The administrator of that system for details.

Content preview:  > If I leave the machine sitting idle for a while, the screen
   goes > black, but the backlight is still on, and I can see very faint colors
   > changing at the top of the screen. This sucks, because ther [...] 

Content analysis details:   (10.3 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
 0.0 TVD_RCVD_IP            Message was received from an IP address
 2.7 RCVD_IN_PSBL           RBL: Received via a relay in PSBL
                            [77.136.38.132 listed in psbl.surriel.com]
 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in
                            bl.spamcop.net
               [Blocked - see <http://www.spamcop.net/bl.shtml?77.136.38.132>]
 0.4 RCVD_IN_XBL            RBL: Received via a relay in Spamhaus XBL
                            [77.136.38.132 listed in zen.spamhaus.org]
 3.3 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
 1.3 RCVD_IN_RP_RNBL        RBL: Relay in RNBL,
                            https://senderscore.org/blacklistlookup/
                            [77.136.38.132 listed in bl.score.senderscore.com]
 1.0 RDNS_DYNAMIC           Delivered to internal network by host with
                            dynamic-looking rDNS
 2.1 NO_FM_NAME_IP_HOSTN    No From name + hostname using IP address



[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 1355 bytes --]

From: qwx <qwx@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] ThinkPad X250 screen blanks against my wishes
Date: Thu, 10 Jan 2019 09:49:58 +0100
Message-ID: <5BDAB1A586F7214BF811C877C6236247@wopr.sciops.net>

> If I leave the machine sitting idle for a while, the screen goes
> black, but the backlight is still on, and I can see very faint colors
> changing at the top of the screen.  This sucks, because there seems to
> be no way to recover.  Every time a leave the office and return I have
> to reboot.

This seems to be an issue with newer intel graphics cards.

As a workaround, you can disable blanking:

; echo blanktime 0 >'#m'/mousectl

x250 is broadwell, you could also try adding its pci did to
/sys/src/cmd/aux/vga/igfx.c as a haswell ulx machine and try using
igfx with monitor=auto.

This will also disable blanking unless you also add the pci did to
the several checks in /sys/src/9/pc/vgaigfx.c.

x240 is haswell ulx and is reported to not work, so this might not
either.

Hope this helps,

qwx

Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[Ethan Gardener]

On Thu, Jan 10, 2019, at 8:49 AM, qwx wrote:
>  pts rule name              description
> ---- ---------------------- --------------------------------------------------
> -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
>                             [score: 0.0000]
>  0.0 TVD_RCVD_IP            Message was received from an IP address
>  2.7 RCVD_IN_PSBL           RBL: Received via a relay in PSBL
>                             [77.136.38.132 listed in psbl.surriel.com]
>  1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in
>                             bl.spamcop.net
>                [Blocked - see <http://www.spamcop.net/bl.shtml?77.136.38.132>]
>  0.4 RCVD_IN_XBL            RBL: Received via a relay in Spamhaus XBL
>                             [77.136.38.132 listed in zen.spamhaus.org]
>  3.3 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
>  1.3 RCVD_IN_RP_RNBL        RBL: Relay in RNBL,
>                             https://senderscore.org/blacklistlookup/
>                             [77.136.38.132 listed in bl.score.senderscore.com]
>  1.0 RDNS_DYNAMIC           Delivered to internal network by host with
>                             dynamic-looking rDNS
>  2.1 NO_FM_NAME_IP_HOSTN    No From name + hostname using IP address
> 
> 
> Email had 1 attachment:
> + Re: [9front] ThinkPad X250 screen blanks against my wishes
>   1k (message/rfc822)

I can understand the lists because 9front-bugs accepted all spam for a while, but "No From name" makes no sense. Oh... unless they mean the From field contains only an email address.  That's ridiculous, all spam comes with a full name in From.  (That's how you know it's spam. *trollface*)  The IP address parts are outside my comprehension.

-- 
2.1.3. Life with eternal upgrades

Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[Stanley Lieber]

isn’t this saying the relay 77.136.38.132 is the culprit? how did that host get involved?

sl

Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[Ethan Gardener]

77.136.38.132 isn't in the headers I received

Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[Stanley Lieber]

On Jan 10, 2019, at 10:02 AM, Ethan Gardener <eekee57@fastmail.fm> wrote:
> 
> 77.136.38.132 isn't in the headers I received

if i’m interpreting correctly, qwx’s origin message was marked spam by wopr.sciops.net because it was relayed to wopr through 77.136.38.132, which is listed in the spam database wopr checks before delivering messages.

i think all of this happened before qwx’s original message ever made it to the 9front mailing list server.

sl

Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes

[Kurt H Maier]

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