Deny MX queries for dynamic IP pools

[Wael Shaheen]

Hi,

On 1/31/10 5:17 PM, "Sven Eschenberg" <sven at whgl.uni-frankfurt.de> wrote:

> Dear Wael,
> 
> In what way is blocking Port 25 any worse than blocking MX/root queries
> for clients? Both solutions neglect the fact, that spam is not a technical
> problem.

This spam issue is major for DSPs and large ISPs. Their reputation is key in
acquiring connections from some major international providers. This brings
the issue to a very high priority for connectivity is the most important
part.
Blocking port 25 is much worse IMHO because it forces users out of the
service, by restricting their ability to use their own mail servers that can
be hosted externally. I believe good mail administrators will force SMTPS
which uses a different port but then again a lot wont, and hence blocking
SMTP service will deny all of these users from accessing their email servers
and most of these users are not technically educated enough to find a
workaround.

On the other hand denying the dynamic user MX/root queries will affect users
that have installed mail servers on their systems or otherwise infected and
both of these scenarios are illegal for dynamically assigned IPs.
 
> Some ISPs think it is a good idea to forward you to a search web page,
> when you mispell some URL, this is done via DNS. Obviously, if the
> customer dislikes this, the customer will (and can) use his/her own
> recursor,

We do not redirect users if they misspelled their destinations and we do not
manipulate DNS replies in any way. Some users may choose to use their own
installed DNS service, but then again if your service provider has a stable
DNS service and a good and stable internet connection then would that
overcome this disadvantage? At the end I think that something has to be
sacrificed.

Sincerely,
Wael Shaheen