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: Greetings! Would like to introduce myself - I am a specialized hacker, and have succeeded in hacking your operating system. At this moment, I have obtained a complete access to account of yours. On top of that, [...] Content analysis details: (15.2 points, 4.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 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/) 1.0 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS 3.6 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr 2) 0.0 FSL_BULK_SIG Bulk signature with no Unsubscribe 0.0 PDS_BTC_ID FP reduced Bitcoin ID 0.5 BITCOIN_XPRIO Bitcoin + priority 0.0 PDS_BTC_MSGID Bitcoin ID with T_MSGID_NOFQDN2 0.0 BITCOIN_SPAM_07 BitCoin spam pattern 07 0.0 MIMEOLE_DIRECT_TO_MX MIMEOLE + direct-to-MX 3.0 BITCOIN_YOUR_INFO BitCoin with your personal info 0.0 HDR_ORDER_FTSDMCXX_DIRECT Header order similar to spam (FTSDMCXX/boundary variant) + direct-to-MX 1.5 BITCOIN_DEADLINE BitCoin with a deadline 0.0 BITCOIN_TOEQFM Bitcoin + To same as From 2.0 TO_EQ_FM_DIRECT_MX To == From and direct-to-MX 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