From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: spam
Date: Sat, 07 Jan 2006 14:41:03 -0500 [thread overview]
Message-ID: <1136662863.22630.15.camel@mindpipe> (raw)
It seems that the most blindingly obvious spam is making it to
alsa-devel.
Can't Sourceforge just trash anything with "Pharmacy" or
"Pharmaceutical" in the subject? I mean, they don't even bother to mess
up the spelling, this should be like fish in a barrel.
Lee
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-07 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 19:41 Lee Revell [this message]
2006-01-07 19:56 ` spam Jaroslav Kysela
2006-01-07 20:02 ` spam Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-07-23 20:18 spam Tom Watson
2005-07-23 20:24 ` spam Lee Revell
2005-07-23 20:30 ` spam Lee Revell
2005-07-24 22:44 ` spam Lee Revell
2005-07-23 3:15 spam Lee Revell
2005-07-23 11:04 ` spam Hinko Kocevar
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=1136662863.22630.15.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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