Hi folks,
----- Original Message -----
From: "David Schwartz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, 26 February, 2001 08:13
Subject: Re: mailtag.com is fixed, I think
[...]
> The *only* solution that actually fixes the problem is to fix the
broken
> autoresponder. The usual way Internet vigilantes coax administrators to
fix
> their broken autoresponders is to create messages from one autoresponder
to
> another -- this usually convinces adminstrators that it is in fact their
> problem.
Hm, I start to feel 'vigilante' here ;-) Now all I need is yet another
auto-reponder that is buggering the list. Or have the auto-responder talk to
itself. Hm.......
Anyway, it looks like it's the season for auto-responders. A few questions
as I'm wondering how we could 'handle' this issue:
1) Is [EMAIL PROTECTED] registered with the list, and, if not, can
anyone track down which 'subscriber' causes the mailtag.com auto responser
to trigger? There's got to be someone (virtual or real) registered with the
list who makes this bloody responder trigger every time a new message
arrives at the list. :-( So this message of mine will trigger yet one more.
Grumble.
I know this is a 5-minute fix and doesn't 'solve' anything, but, well, it
reduces the amount of irritation on the list, you know.
2) As we might take the task upon us to educate all those admins with broken
auto-responders and out-of-office tools out there, I suppose it's one of
those Don Quichot things. One can only continue doing so for so long as
morons simply cannot loose: they win by sheer numbers. What are our options
for the long term future (some dumb ideas follow below):
2a) can the mailing list software 'filter' incoming messages and have the
mailing list drop any message which does not have a specific tag, say
'[SSL-U]' at the start of the subject line (where leading 'Re:' strings
should be ignored). This style of behaviour is used by a lot of people using
various newsgroups to filter incoming spam, etc. (For instance
alt.binaries.moderated.pinup-art: 'ABMP-A') The drawback is that you'll need
to send your email twice if you wish to address both openssl-users [SSL-U]
and openssl-dev [SSL-D], for example.
2b) does the mailing list software have any 'lockout' options available
(such as: locking out users which generate over, say, 200+ emails a day,
though this doesn't sound 'good' to me either, but it an idea).
(Right now, I'm running a filter on [EMAIL PROTECTED] to delete any
email from that one, but that's a quick fix too.)
any other ideas?
Groetjes/Greetinx,
Ger
----- Original Message -----
From: "Rich Salz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, 26 February, 2001 05:29
Subject: mailtag.com is fixed, I think
[...]
> They also said they are not going to be nice any longer. After all,
> they "explained," it is not their mailing list sending spam, but that
> it is the fault of, I think they believe, the host of the openssl-users
> mailing list. They've been doing autoresponses for three years, and
> have never had a problem before, so "do not coming whining to us" if it
> happens again.
Hell, I don't like to admit it, but I have written software that peformed OK
for a few years. And all of a sudden I got a serious bug report that made me
blush (after I tracked down the offending code). I even might be writting
such software these days. ("But Mister Customer, can't be my fault as it
works on *my* console..." :-) )
----------------------------------------------------------------------------
--
Ger Hobbelt a.k.a. Insh_Allah mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------------
--
Peter Pan can fly when he thinks his Happy Thought.
I want to fly too.
My Happy Thought is... one part Prozac and one part LSD...
Wow! Awesome, dude!
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
