From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Cutting down spam on this list
Date: Wed, 22 Mar 2006 12:30:23 -0700 [thread overview]
Message-ID: <4421A5CF.8010204@redfish-solutions.com> (raw)
In-Reply-To: <441F2AE4.1050601@redfish-solutions.com>
Ok, just saw:
>Received: from sc8-sf-list2-b.sourceforge.net (sc8-sf-list2-b.sourceforge.net [10.3.1.8])
> by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
> id 08A48132A0; Wed, 22 Mar 2006 11:25:11 -0800 (PST)
>Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net)
> by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30)
> id 1FM8wl-00059t-N3
> for alsa-devel@lists.sourceforge.net; Wed, 22 Mar 2006 11:24:43 -0800
>Received: from alsa.jcu.cz ([160.217.9.25])
> by mail.sourceforge.net with esmtp (Exim 4.44)
> id 1FM8wj-0005jA-1U
> for alsa-devel@lists.sourceforge.net; Wed, 22 Mar 2006 11:24:43 -0800
>Received: by alsa.jcu.cz (ALSA's E-mail Delivery System)
> id 763211CE; Wed, 22 Mar 2006 20:24:38 +0100 (MET)
>Delivered-To: alsa-devel@alsa-project.org
>Received: from www.aaaaldo.com (aaaaldo.com [66.103.151.35])
> by alsa.jcu.cz (ALSA's E-mail Delivery System) with SMTP id EDC601CD
> for <alsa-devel@alsa-project.org>; Wed, 22 Mar 2006 20:24:37 +0100 (MET)
>Content-Type: text/html;
>From: "Realestate.com" <moreinfo@triplealdo.com>
>MIME-Version: 1.0
>To: Friend <alsa-devel@alsa-project.org>
>Message-ID: <44219c3e@www.aaaaldo.com>
>X-Complaints-To: abuse@www.aaaaldo.com
>Subject: [Alsa-devel] Let RealEstate.com Prospect for You
>X-Original-Date: Wed, 22 Mar 2006 18:49:34 +0000
>Date: Wed, 22 Mar 2006 18:49:34 +0000
>
Someone tell me again why we need the alsa.jcu.cz gateway? Since most
people email directly to alsa-devel@lists.sourceforge.net, this backdoor
would seem to be nothing but a spam collector.
-Philip
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-22 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 22:21 Cutting down spam on this list Philip Prindeville
2006-03-22 19:30 ` Philip Prindeville [this message]
2006-03-22 19:34 ` Takashi Iwai
2006-03-22 19:37 ` Philip Prindeville
2006-03-22 19:59 ` Takashi Iwai
2006-03-22 20:16 ` Sergei Shtylylov
2006-03-28 12:33 ` Jaroslav Kysela
2006-03-28 13:13 ` Takashi Iwai
2006-03-28 17:28 ` Philip Prindeville
2006-04-04 16:42 ` Philip Prindeville
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=4421A5CF.8010204@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.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