[100913] in North American Network Operators' Group
Re: unwise filtering policy from cox.net
daemon@ATHENA.MIT.EDU (Chris Edwards)
Wed Nov 21 20:38:08 2007
Date: Thu, 22 Nov 2007 01:30:09 +0000 (GMT)
From: Chris Edwards <chris@eng.gla.ac.uk>
To: "'nanog@merit.edu'" <nanog@merit.edu>
In-Reply-To: <18244.43800.887315.517969@world.std.com>
Errors-To: owner-nanog@merit.edu
On Wed, 21 Nov 2007, Barry Shein wrote:
| Sean's point was that you can't cause, e.g., eg@example.com alone to
| go to a server other than the same set of servers listed for
| AnythingElse@example.com.
Yes of course - but only a fundamental problem where the MX servers are
hopelessly overloaded.
This is different from the situation described in the original post, where
filtering policy is being applied indiscriminately regardless of recipient
LHS, which is generally a sign of substandard software or foolish admin.
As others have said, normal practice is to apply different filtering
policy to certain LHS values (abuse@) and to provision enough MX capacity
such that the service as a whole is functional (including receiving abuse
reports).
