Subject: sending problems

From: Kendahl Adjorlolo <[email-masked]>
Date: Mon, 13 May 1996 14:11:22 -0700 (PDT)

Since Wednesday, May 8, we have been unable to send messages to a
distribution list in "hspers" that we previously had no problem with.  I
asked our bank support group about it and they suggested to add "@u" to all
of the addresses that previously went out without it, rationalizing that
the new Pine had new configurations.  I started to do this,
then realized that we have another list, equally long, which has given us
no trouble in sending during the same time frame, despite that fact that
it doesn't have the "@u" tail.  Before I go ahead and add "@u." to this
rather long list, I'd like some input on why one list is fine and the
other isn't.  And advice on what we can do to make them both work smoothly.

When we do try to send to the problem list we get a message "unable to
send..." and the address shown is rather close to the top of the list.  I
believe all the addresses listed after this one aren't accepted.  In the
end, nothing is sent at all.  Very frustrating as the information we wish
to send should have gone out already...

Thank you.
kendahl
3-9406
HS Personnel

---

From: Will Hall <[email-masked]>
Date: Mon, 13 May 1996 14:25:21 -0700 (PDT)

Just to confirm our phone call, the problem is almost certainly due to the
invalid address "dao" that you had in the hspers list.  By removing tht
and testing the address "amyd", you should be able to get the announcement
out.  Sorry for the delay in resolving this.

-- Will Hall -- UW Client Services -- 206-543-5521 -- Box 355670 --