|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Sender access restrictions by connecting back to the MX/A server(s) - An example
From: Jim Seymour (jseymour
LinxNet.com)
Date: Thu Oct 02 2003 - 08:36:54 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> - An example
>
> I take one example about what happens : a mail coming from one of our
> internal systems, onyx.arts.kuleuven.ac.be . The mail has a from=
> useronyx.arts.kuleuven.ac.be This host has several mx's :
>
> IN MX 5 onyx.arts.kuleuven.ac.be.
> IN MX 10 limbak.cc.kuleuven.ac.be.
> IN MX 10 kromsin.cc.kuleuven.ac.be.
> IN MX 20 cavin.kuleuven.be.
> IN MX 30 cavin01.kuleuven.be.
> IN MX 30 cavin02.kuleuven.be.
> IN MX 30 cavin03.kuleuven.be.
>
> Four of them are reachable from the Internet, the highest priorties
> aren't. The from address exists, bounces/replies _do_ come back (for
> those who don't stick to only the first mx), ...
> so the message is refused...
[snip]
>
In my ignorance (I assume it's my ignorance at work here), I have to
ask...
Why would one purposefully advertise MX' that one knows for a fact
are not reachable? Not just one, and not just any, but the *highest*
priority MX'... *three* of 'em.
Why would someone do this? Why force every other MTA on the planet
to try at least three MX' one *knows* they can't reach, before
hitting one that might work?
--
Jim Seymour | PGP Public Key available at:
jseymourLinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html
http://jimsun.LinxNet.com |
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]