From: John Rigg <ad@carbon-black.co.uk>
To: alsa-devel@lists.sourceforge.net
Cc: James Courtier-Dutton <james.dutton@gmail.com>
Subject: alsa-devel mail problem
Date: Thu, 8 Dec 2005 19:50:51 +0000 [thread overview]
Message-ID: <20051208195051.GA4340@localhost.localdomain> (raw)
Some of you might have seen James Courtier-Dutton's warning yesterday
about a piece of spam purporting to come from sourceforge.
When I received the spam I reported it to the ISP hosting the fake
web page and was pleased to see that the site had been removed a few
hours later. I replied to James' email on the list to point this out,
but I found that my email address had been blocked by the list.
I'm not sure yet if it was a disgruntled phisher adding me to a blacklist
or whether the sourceforge mail filters didn't like the reference to
the spam in my mail. I had to open a new subscription to send this.
The obvious moral: if you're going to report these idiots to their ISP,
don't use an important email address!
John
-------------------------------------------------------
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
reply other threads:[~2005-12-08 19:50 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=20051208195051.GA4340@localhost.localdomain \
--to=ad@carbon-black.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=james.dutton@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.