From: "Near Wifes" <iahtuyxpaxn@adslplus.ch>
To: linux-pm@osdl.org
Subject: Aggressive Investors Alert
Date: Fri, 16 Feb 2007 06:35:35 -0100 [thread overview]
Message-ID: <9E2AEE07707706A.ED572DB230@adslplus.ch> (raw)
[-- Attachment #1.1: Type: text/html, Size: 1816 bytes --]
[-- Attachment #2: SpamAssassinReport.txt --]
[-- Type: text/plain, Size: 1311 bytes --]
Spam detection software, running on the system "daredevil.osdl.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: *** POTENTIAL POWERHOUSE GAINS POSSIBLE WITH ***HXPN***
Harris Exploration Inc Acquisition, Exploration and Development Tick:
HXPN Opening: $1.50 GET IN ON FRIDAY FEBRUARY 16th 2007! Extended Day
Target: $2.00 [...]
Content analysis details: (7.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.8 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DHCP)
0.1 OSDL_NIGERIAN_GOLD BODY: "go*ld"
0.2 HTML_SHOUTING3 BODY: HTML has very strong "shouting" markup
0.0 HTML_MESSAGE BODY: HTML included in message
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score: 0.5000]
2.0 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.2 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
0.8 UPPERCASE_25_50 message body is 25-50% uppercase
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2007-02-16 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 7:35 Near Wifes [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-30 20:35 Aggressive Investors Alert Air
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=9E2AEE07707706A.ED572DB230@adslplus.ch \
--to=iahtuyxpaxn@adslplus.ch \
--cc=linux-pm@osdl.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