From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [SPAM] Re: [9front] ThinkPad X250 screen blanks against my wishes
Date: Thu, 10 Jan 2019 11:56:37 +0000 [thread overview]
Message-ID: <1547121397.2251560.1630797592.1A6BD1DA@webmail.messagingengine.com> (raw)
In-Reply-To: <5BDAB1A586F7214BF811C877C6236247@wopr.sciops.net>
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
next prev parent reply other threads:[~2019-01-10 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 8:49 qwx
2019-01-10 11:56 ` Ethan Gardener [this message]
2019-01-10 14:23 ` Stanley Lieber
2019-01-10 15:02 ` Ethan Gardener
2019-01-10 15:11 ` Stanley Lieber
2019-01-10 16:22 ` Kurt H Maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1547121397.2251560.1630797592.1A6BD1DA@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).