Re: [Exim] Blacklisting dynamic IP ranges versus dyndns.org

Top Page
Delete this message
Reply to this message
Author: Dan Egli
Date:  
To: Matthew Palmer
CC: exim-users
Subject: Re: [Exim] Blacklisting dynamic IP ranges versus dyndns.org
You have been coddled. The ISP on my DSL is the phone company and like most
phone companies they don't give $0.02 about me as long as they can collect
my $100/mo for the phone lines and DSL.

Not to mention the fact that most ISPs are so large that it takes some time
to get a hold of anyone who can tell you anything. In my examples, I had
ready access to all the information. If I had to call my ISP I would not be
able to guarantee getting any information within the next three DAYS. That's
if I'm LUCKY!

----- Original Message -----
From: "Matthew Palmer" <mjp16@???>
To: "Dan Egli" <dan@???>
Sent: Wednesday, October 30, 2002 7:02 PM
Subject: Re: [Exim] Blacklisting dynamic IP ranges versus dyndns.org


> On Wed, 30 Oct 2002, Dan Egli wrote:
>
> > I can think of a good reason:
> > TRACKABILITY! I have a DynDns address (as you can see from my return

email
> > address), and I relay a lot of mail through Exim on this box. The reason

I
>
> Your example has credibility. However, all you're saving there is one

phone
> call - to your ISP, to check what happened to it at their server.
>
> > Example #2:
> > I sent a message to a customer. They called around two hours later

saying
>
> No difference to the example above, really. Again, there's a mail problem
> somewhere, and the message gets traced through the system and the problem

is
> resolved.
>
> Maybe I'm spoilt by a decent ISP, but trying vainly to hack an MTA to

solve
> an ephemeral issue which is easily solved by doing things As They Were

Meant
> To Be seems a bit pointless to me.
>
> > If I was relaying all my mail through my ISP's mail server (and frankly,

I
> > don't trust my DSL provider's mail server any further than I can throw

it!)
> > I would not have been able to handle either of these situations!
>
> Yes you would, by checking details on your server then contacting your ISP
> to track the message through their system.
>
> Again, maybe I've just been coddled by a responsive ISP who is always
> available to handle meaningful problems.
>
>
> --
> -----------------------------------------------------------------------
> #include <disclaimer.h>
> Matthew Palmer, Geek In Residence
> http://ieee.uow.edu.au/~mjp16
>
>