Gnus development mailing list
 help / color / mirror / Atom feed
From: David Wuertele <dave-gnus@bfnet.com>
Subject: Re: road warrior trying to simplify a mail setup
Date: Fri, 28 Feb 2003 16:32:22 -0800	[thread overview]
Message-ID: <m3smu8apux.fsf@bfnet.com> (raw)
In-Reply-To: <86wuk2axo8.fsf@red.stonehenge.com>

Randal> If you're interested in actually having a conversation, get
Randal> rid of your anti-spam software.
Randal> It sucks.

It was misconfigured.

Sorry if TMDA caused you grief.  It hasn't caused me any.  In fact, it
has solved *all* the spam problems I had.  If it has introduced new
ones, I haven't discovered them yet.  As long as I don't, you can have
my spam software when you pry it from my...

Randal> Moral of the story: if you install anti-spam software that
Randal> requires a positive confirmation before unblocking an address
Randal> (a) there'll be people that never bother, and so you never
Randal> hear from them, and (b) sometimes your software sucks and
Randal> blocks people even when they follow the actions to the letter.

a) if they don't bother, and I don't hear from them, it must not have
   been very important.  There are many more ways to get hold of me
   than by email.

b) sometimes user error is the real cause of suckage.  that was the
   case this time.  Mea culpa, I actually tried to do something
   different than how the "manual" said to do it.

Randal> If you don't want spam, don't have an email adddress.  Get
Randal> over it.

I think you're just lashing out due to frustration.  I don't have any
other explanation for an engineer deciding that there is no way to
solve a problem.

I haven't seen a single spam since I started using TMDA, and the only
issue I've had was your email.  There was a period of an hour or two
when I had set up my dot qmail files incorrectly --- so the problem
wasn't even related to TMDA, it was my misconfiguration of qmail.

Dave




  reply	other threads:[~2003-03-01  0:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 17:04 Randal L. Schwartz
2003-02-05 21:47 ` Vasily Korytov
2003-02-05 21:49   ` Randal L. Schwartz
2003-02-06  9:30     ` James Leifer
2003-02-06 21:37     ` Kirk Strauser
2003-02-06 15:46 ` Kai Großjohann
2003-02-07  1:27 ` Stainless Steel Rat
2003-02-07  2:04   ` Randal L. Schwartz
2003-02-07  2:24     ` Stainless Steel Rat
2003-02-07  5:41       ` Randal L. Schwartz
2003-02-07 16:28         ` Stainless Steel Rat
2003-02-07 16:39           ` David S Goldberg
2003-02-07 18:14             ` Randal L. Schwartz
2003-02-07 18:49               ` David S Goldberg
2003-02-07 18:13           ` Randal L. Schwartz
2003-02-07 19:38             ` Stainless Steel Rat
2003-02-07 19:53               ` Randal L. Schwartz
2003-02-07 20:06                 ` Stainless Steel Rat
2003-02-07 20:18                   ` Randal L. Schwartz
2003-02-07 23:18                     ` Stainless Steel Rat
2003-02-07 21:45             ` Kai Großjohann
2003-02-07  7:18 ` Michel Schinz
2003-02-07  9:07   ` Niklas Morberg
2003-02-07 15:44     ` Randal L. Schwartz
2003-02-07 16:34       ` David S Goldberg
2003-02-07 15:52   ` Kai Großjohann
2003-02-14 21:53 ` David Wuertele
2003-02-15  5:50   ` Randal L. Schwartz
2003-02-15  6:02     ` Randal L. Schwartz
2003-03-01  0:32       ` David Wuertele [this message]
2003-03-03  8:50         ` Bjørn Mork
2003-03-03 17:27           ` David Wuertele
2003-03-04 12:11             ` Bjørn Mork

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=m3smu8apux.fsf@bfnet.com \
    --to=dave-gnus@bfnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).