>
> I did a quick beeper test and found that an email sent to
> attmail from vxmacb (at 10:37 am EST) arrived 1 hour ten minutes later
> on the beeper.
>
> Just FYI.
>
> I should have cc'ed somewhere so that I could see where the
> bottle-neck was, but I didn't think of it...
>
Urgh.
I'm suspecting an LNGS network problem, given that the delays are common
to you and Dan.
Here are the paths the messages take:
For the SkyTel beeper:
vxmacb -> DECNET to vaxgs -> attmail.com -> SkyTel -> beeper
-> SMTP (via vaxgs I think) -> attmail.com -> SkyTel -> beeper
For Dan's beeper:
vxmacb -> DECNET to vaxgs -> umich -> Dan's beeper company -> beeper
-> SMTP -> umich -> Dan's beeper company -> beeper
(Dan, do you use SkyTel locally?)
So to figure out where the delay is, we need to check these legs separately.
It would be best to log on to my attmail account,
to check
vxmacb -> attmail
attmail -> beeper
Unfortunately I haven't done that for about a year. I don't remember
my attmail password but it may be possible to excavate it from my
office or old email; let me look.
In the meantime, you could try: (at about the same time)
-- email from vxmacb to the beeper (you already did that), via the two
paths (see addresses.text in [michpub.erp.erpgc])
-- email from vaxgs to the beeper
-- calling SkyTel up to have them send a message
directly (see the instructions) to the beeper.
If this last is slow,
then we know it's a SkyTel problem. Otherwise it could be either LNGS
or attmail. If the problem is attmail, it may be time to get rid of
them; when I set this up, this was the only (at least way easiest) way
to send email to a pager, but there are better ways now.
Dan, you'll have to check your beeper path; did the message arrive
in Michigan on time?
Kate.