From: "Florine Barrow" <brucem@brynnetaylor.com>
To: linus@osdl.org
Subject: Ever wanted to ejaculate 5 times more?
Date: Tue, 26 Jun 2007 23:49:52 +0600 [thread overview]
Message-ID: <01c7b84c$b0f4d890$c8291147@brucem> (raw)
[-- Attachment #1: Type: text/plain, Size: 40 bytes --]
Rock hard erections
http://parufly.com
[-- Attachment #2: SpamAssassinReport.txt --]
[-- Type: text/plain, Size: 869 bytes --]
Spam detection software, running on the system "daredevil.linux-foundation.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: Rock hard erections http://parufly.com [...]
Content analysis details: (6.7 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.8 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr
2)
0.9 DATE_IN_PAST_06_12 Date: is 6 to 12 hours before Received: date
2.0 BAYES_80 BODY: Bayesian spam probability is 80 to 95%
[score: 0.9332]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2007-06-26 17:49 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='01c7b84c$b0f4d890$c8291147@brucem' \
--to=brucem@brynnetaylor.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