From: "Olen Stephens" <KresgeAlsace's@abec.com>
To: linus@osdl.org
Subject: fw: Damien Blanton wrote:
Date: Fri, 26 Jan 2007 16:29:21 +0000 (UTC)
Date: Sat, 27 Jan 2007 16:52:07 -0060 [thread overview]
Message-ID: <01c74233$7b08ad40$6c822ecf@KresgeAlsace's> (raw)
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
I have heard something big will happen on friday with thet one.
It has rise already on +21.8 %
Look at lvl2. Pretty nice ye ?
Check NMXC(New Mexico Software, Inc) and think how easily this issue will move! For this moment at this time it’s cost is x.06
Also news are comming!They will make this issue very HOT.
And it will fly like others.
717378746933776E7A457871746C
Atheneus
[-- Attachment #2: SpamAssassinReport.txt --]
[-- Type: text/plain, Size: 944 bytes --]
Spam detection software, running on the system "murdock.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: I have heard something big will happen on friday with
thet one. It has rise already on +21.8 % Look at lvl2. Pretty nice ye ?
Check NMXC(New Mexico Software, Inc) and think how easily this issue
will move! For this moment at this time it’s cost is x.06 [...]
Content analysis details: (5.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.3 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DHCP)
2.1 DATE_IN_FUTURE_24_48 Date: is 24 to 48 hours after Received: date
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2007-01-26 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='01c74233$7b08ad40$6c822ecf@KresgeAlsace'\''s' \
--to=kresgealsace's@abec.com \
--cc=linus@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