nanog mailing list archives
Re: unwise filtering policy from cox.net
From: Paul Jakma <paul () clubi ie>
Date: Thu, 22 Nov 2007 09:03:51 +0000 (GMT)
On Wed, 21 Nov 2007, Barry Shein wrote:
xx () example com is going to go to whatever MX example.com returns.
Yes, I'm aware.
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.
Right, his point was that load or policy (" administrators may make changes which affect all addresses) would cause a problem, and this was, for some reason, due to routing of email addresses.
I took issue with the policy side of the comment. While it's possible, it's got nowt to do with limitations in SMTP routing, it's just operator error.
If that (eg () example com) overloads those servers, even if they're valiantly trying to pass the connection off to another machine, then you have to use some other method like eg () special example com or eg () other-domain com and hope the clients will somehow use that tho for BIGCOMPANY there's a tendency to just bang in abuse () BIGCOMPANY COM.
Right, I do understand that. There are obvious ways to horizontally scale inbound mail using MX records and more, so the load issue shouldn't be an issue for any given organisation. Least not more than once.
However, I didn't comment on the load part of Sean's point.
If you think I'm wrong (or Sean's wrong) even for a milisecond then trust me, this is going right over your head. Think again or email me privately and I'll try to be more clear.
I don't think this is over my head. regards, -- Paul Jakma paul () clubi ie paul () jakma org Key ID: 64A2FF6A Fortune: Love thy neighbor as thyself, but choose your neighborhood. -- Louise Beal
Current thread:
- Re: BOTNET reference involving oscilloscope, (continued)
- Re: BOTNET reference involving oscilloscope Leigh Porter (Nov 23)
- Re: BOTNET reference involving oscilloscope Adrian Chadd (Nov 23)
- Re: unwise filtering policy from cox.net Chris Edwards (Nov 21)
- Re: unwise filtering policy from cox.net Robert E. Seastrom (Nov 21)
- Re: unwise filtering policy from cox.net Leigh Porter (Nov 21)
- Re: unwise filtering policy from cox.net Suresh Ramasubramanian (Nov 22)
- Re: unwise filtering policy from cox.net Adrian Chadd (Nov 22)
- Re: unwise filtering policy from cox.net Suresh Ramasubramanian (Nov 22)
- Re: unwise filtering policy from cox.net Joel Jaeggli (Nov 26)
- RE: unwise filtering policy from cox.net Jamie Bowden (Nov 26)
- Re: unwise filtering policy from cox.net Paul Jakma (Nov 22)
- Re: unwise filtering policy from cox.net Eliot Lear (Nov 21)
- Re: unwise filtering policy from cox.net Suresh Ramasubramanian (Nov 21)
- Re: unwise filtering policy from cox.net Eliot Lear (Nov 21)
- Re: unwise filtering policy from cox.net Suresh Ramasubramanian (Nov 21)