Spam detection software, running on the system "mail.pglaf.org",
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: Hello there! Unfortunately, there are some bad news for you.
Around several months ago I have obtained access to your devices that you
were using to browse internet. Subsequently, I have proceeded with tracking
do [...]
Content analysis details: (22.2 points, 4.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4999]
1.6 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
1.4 PYZOR_CHECK Listed in Pyzor
(https://pyzor.readthedocs.io/en/latest/)
-0.0 T_SCC_BODY_TEXT_LINE No description available.
0.0 HDR_ORDER_FTSDMCXX_NORDNS Header order similar to spam
(FTSDMCXX/boundary variant) + no rDNS
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
0.0 FSL_BULK_SIG Bulk signature with no Unsubscribe
0.0 PDS_BTC_MSGID Bitcoin ID with T_MSGID_NOFQDN2
2.0 BITCOIN_XPRIO Bitcoin + priority
2.0 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP
addr 1)
0.4 PDS_BTC_ID FP reduced Bitcoin ID
0.0 HDR_ORDER_FTSDMCXX_DIRECT Header order similar to spam
(FTSDMCXX/boundary variant) + direct-to-MX
3.5 BITCOIN_SPAM_07 BitCoin spam pattern 07
0.3 TO_EQ_FM_DIRECT_MX To == From and direct-to-MX
2.8 BITCOIN_YOUR_INFO BitCoin with your personal info
0.0 MIMEOLE_DIRECT_TO_MX MIMEOLE + direct-to-MX
2.0 BITCOIN_MALWARE BitCoin + malware bragging
2.5 DOS_OE_TO_MX Delivered direct to MX with OE headers
2.2 MALWARE_NORDNS Malware bragging + no rDNS
0.0 XPRIO Has X-Priority header
0.0 NO_FM_NAME_IP_HOSTN No From name + hostname using IP address
Spam detection software, running on the system "mail.pglaf.org",
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: Hello there! Unfortunately, there are some bad news for you.
Around several months ago I have obtained access to your devices that you
were using to browse internet. Subsequently, I have proceeded with tracking
do [...]
Content analysis details: (19.4 points, 4.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
0.2 CK_HELO_GENERIC Relay used name indicative of a Dynamic Pool or
Generic rPTR
0.0 TVD_RCVD_IP Message was received from an IP address
1.6 DATE_IN_PAST_03_06 Date: is 3 to 6 hours before Received: date
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
1.4 PYZOR_CHECK Listed in Pyzor
(https://pyzor.readthedocs.io/en/latest/)
-0.0 T_SCC_BODY_TEXT_LINE No description available.
0.0 FSL_BULK_SIG Bulk signature with no Unsubscribe
1.9 STATIC_XPRIO_OLE Static RDNS + X-Priority + MIMEOLE
0.0 PDS_BTC_MSGID Bitcoin ID with T_MSGID_NOFQDN2
2.0 BITCOIN_XPRIO Bitcoin + priority
0.4 PDS_BTC_ID FP reduced Bitcoin ID
0.0 HDR_ORDER_FTSDMCXX_DIRECT Header order similar to spam
(FTSDMCXX/boundary variant) + direct-to-MX
3.5 BITCOIN_SPAM_07 BitCoin spam pattern 07
0.3 TO_EQ_FM_DIRECT_MX To == From and direct-to-MX
2.8 BITCOIN_YOUR_INFO BitCoin with your personal info
0.0 MIMEOLE_DIRECT_TO_MX MIMEOLE + direct-to-MX
2.0 BITCOIN_MALWARE BitCoin + malware bragging
2.5 DOS_OE_TO_MX Delivered direct to MX with OE headers
0.0 XPRIO Has X-Priority header
0.0 NO_FM_NAME_IP_HOSTN No From name + hostname using IP address
