From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Alexander Lyamin <flx@namesys.com>,
Russell Coker <russell@coker.com.au>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Recent spam
Date: 06 Jun 2003 09:01:07 -0400 [thread overview]
Message-ID: <1054904467.23130.223.camel@tiny.suse.com> (raw)
In-Reply-To: <3EE04C02.2090707@namesys.com>
On Fri, 2003-06-06 at 04:08, Hans Reiser wrote:
> >No-one has asked the administrators of your mailing list to do anything
> >special, just to refrain from doing unusual things.
> >
> >If you want a quick temporary fix then change the list address. The
> >subscribers will be able to deal with it well enough (it's happened before)
> >but the spammers will take some time to catch up.
> >
> >
> >
> Remove Russell from the list.
Hans, a short review:
1) For many months people (not just Russell) have been asking namesys to
fix various simple problems with the mail server configuration. These
problems make anyone using automatic spam reporting tools report namesys
as spammers.
2) Somehow, various spam databases think namesys is a spammer.
3) namesys has not fixed the listserver.
4) namesys gets mad about being in the spam database.
You can have #3 or #4, but not both. Either fix the list, or ignore the
problem, but don't leave the list broken and get angry when you end up
in a spammer database. It doesn't really matter how you got there, the
fault lies with namesys, not the list users.
If all the time and energy spent talking about spam on the reiserfs list
actually went into fixing the list, this conversation would have ended a
long time ago.
-chris
next prev parent reply other threads:[~2003-06-06 13:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 6:29 Recent spam Manuel Krause
2003-06-02 6:33 ` Marc-Christian Petersen
2003-06-02 7:24 ` Soeren Sonnenburg
2003-06-02 8:59 ` Russell Coker
2003-06-05 13:26 ` Hans Reiser
2003-06-05 13:39 ` Chris Mason
2003-06-05 14:39 ` Hans Reiser
2003-06-05 14:52 ` Chris Mason
2003-06-05 19:48 ` Russell Coker
2003-06-06 8:08 ` Hans Reiser
2003-06-06 9:02 ` Soeren Sonnenburg
2003-06-06 14:33 ` Hans Reiser
2003-06-06 14:38 ` Oleg Drokin
2003-06-06 17:42 ` Russell Coker
2003-06-06 22:20 ` Joachim Bremer
2003-06-06 22:34 ` Hans Reiser
2003-06-06 23:05 ` Hans Reiser
2003-06-06 13:01 ` Chris Mason [this message]
2003-06-06 13:44 ` Hubert Mantel
2003-06-06 15:30 ` Kristine Diana Daniels
2003-06-06 15:39 ` Chris Mason
2003-06-05 14:57 ` Chris Dukes
2003-06-05 15:11 ` Chris Mason
2003-06-05 15:26 ` Nikita Danilov
2003-06-05 16:30 ` Chris Mason
2003-06-05 15:29 ` Ragnar Kjørstad
2003-06-06 5:31 ` Oleg Drokin
2003-06-05 15:23 ` Hans Reiser
2003-06-05 15:25 ` Hans Reiser
2003-06-05 16:26 ` Chris Mason
2003-06-02 13:02 ` OT: " Asheesh Laroia
2003-06-02 13:06 ` Chris Mason
2003-06-02 13:38 ` Chris Dukes
2003-06-02 13:47 ` Pierre Abbat
2003-06-02 15:54 ` Matthias Andree
2003-06-06 13:09 ` Alexander Lyamin
2003-06-20 19:08 ` John Dalbec
2003-06-08 19:13 ` Alexander Lyamin
2003-06-08 20:05 ` Christophe Saout
2003-06-14 11:03 ` Manuel Krause
2003-07-12 5:44 ` Carl-Daniel Hailfinger
[not found] <no.id>
2003-06-02 7:28 ` The Amazing Dragon
2003-06-05 22:45 ` The Amazing Dragon
-- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:17 Eric Sandeen
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=1054904467.23130.223.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=flx@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.