Re: Shaw is pissing me off

[Dan Brosemer <odin@svartalfheim.net>]

On Wed, Jun 26, 2002 at 11:10:25PM -0400, Jim Dew wrote:
> i dont think the workaround is necessary anymore.. i undid the workaround
> on banpei, and it is working correctly still.

Here's the discussion Jim and I had just after he posted this cleaned up:

jdew:
ah.. and for the shaw workaround.. no worries..
well.. worries i suppose..

but for the time being it works as it should for me again

dan:
is this is back to my old workaround, or back to what it should be

jdew:
umm.. i went back to the old forwarders line i had... 
forwarders  24.207.26.101 207.6.128.247 144.162.120.230

dan:
So back to the old workaround, then.  Try going to the ICANN setup.  No
forwarders line.

jdew:
now how do i test this.. i removed the forwarders line.. and ndc restart'ed...  do i have to wait till things start bouncing?

dan:
no... run sendmail -bt as in
http://lists.cleannorth.org/archive/techies/2002-06/msg00002.html

jdew:
jdew@ratatosk[~]% sendmail -bt
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
Enter <ruleset> <address>
> olgc.on.ca
No address!
> check_mail olgc.on.ca
check_mail         input: olgc . on . ca
Basic_check_mail   input: olgc . on . ca
tls_client         input: $| MAIL
TLS_connection     input:
TLS_connection   returns:
tls_client       returns:
CanonAddr          input: < olgc . on . ca >
canonify           input: < olgc . on . ca >

dang...
pausing at Canonify2
guess its gonna time out :\

--- end

So it works with the old workaround again.  This is a good thing.  I'll make
the CN nameservers stop querying mine down here in a bit, but it's still
indicative of major problems at Shaw, and I wouldn't trust them not to break
this again.  I think we need a long-term solution.

-Dan

-- 
"Burnished gallows set with red
 Caress the fevered, empty mind
 Of man who hangs bloodied and blind
 To reach for wisdom, not for bread."  -- Deoridhe Grimsdaughter