🚀 go-pugleaf

In article <1992May01.213144.5296@chinet.chi.il.us> prb@chinet.chi.il.us (Paul Botts) writes:
>I am having persistant trouble with large batches of mail bouncing back
>to Chinet from mcdchg - I keep getting it back marked "unable to contact
>system mcdchg". Note that this is not mail *to* anyone at mcdchg, but
>rather to elsehwere on the net, and it's being routed through homebru
>and then mcdchg.
>Can anyone advise me on how I might reroute this mail around mcdchg? Or
>is there another solution?

I believe I can at least provide some information on what's happening, and a
workaround if you care to take it.

It seems mcdchg is undergoing some serious organ transplants, and has been
expriencing fairly long outages--particularly over weekends, when it's
unattended.  For instance, as of this Monday morning, there were 170+ jobs
queued on homebru/clout for mcdchg because sometime Friday it stopped providing
a login prompt after answering the phone.  Ron Heiby has sent mail apologizing
for the outages, and is working on the issue on an ongoing basis, so we should
expect the situation to be ameliorated in the near future.

In either the short term, or the long term, you can avoid mcdchg by not using
the automated path generation facilities of your mailer (i.e., don't mail to
foo@bar.x.y.z)  Rather, you can either explicitly describe the bang-path to
your intended destination--with all the problems that entails--or you can force
a path to a known Internet site, and let it resolve the address, i.e., send to
'clout!foo@bar.x.y.z'.  Be warned, however--this form has its own problems
with ambiguities, and there's no guarantee that the address router on your
selected site won't find 'mcdchg' an attractive route from there...

		Dave Ihnat
		ignatz@homebru.chi.il.us (preferred return address)
		ignatz@chinet.chi.il.us