North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
- From: Suresh Ramasubramanian
- Date: Mon Mar 21 23:06:29 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=aZO/C97fJxsLN0vgOLNqfGDcleaL2EEkNqlMhgon9gln2XytlBQEKNfX71JG0MvcZbCrPi85kWY8OhMX9rItsptrNKYMCAtAsXpMbIWwjuuGbtb5k4vHBiU9qMj3ywgMDEPCghL/vxFS6CPqr2MtwGOMrDS+YAYyvSeYS9oGY0o=
On Mon, 21 Mar 2005 10:58:00 -0500, Jay R. Ashworth <email@example.com> wrote:
> This sounds like an excellent sales point for value added mail
It is not just clueless end user exchange admins who deploy dumb filter rules.
If I had a nickel for every time I've run into stupid spam filtering
(read: filtering that affects mail from my over 40 million users,
because an admin was too dumb to read forged headers) at surprisingly
large operators [ISPs, huge corporate networks etc] I'd be rich.
Luckily, quite a few people who turn on dumb spam filters do turn them
off when contacted and told about their bad filtering. Some make the
mistake of not doing so - and they'll be destined to lose email for
their users, on a permanent basis.
Its that old Spiderman quote - With great power comes great
responsibility. Having root / enable / postmaster access at a site
means its not enough to know how to do "access list 101 deny" or "vi
/etc/mail/access" .. it means that the guy should know when to do it -
and when not to. And he should be reachable, and should know enough
to realize he's screwed up, and to fix it. Sadly, this is rather less
common than simply knowing how to throw filters in - that's the easy
part. Kind of like the difference between a mining engineer
triggering carefully shaped and placed demolition charges, and Wile E
Coyote lighting the fuse on a bundle of dynamite.
Suresh Ramasubramanian (firstname.lastname@example.org)