| Hi,
The most common (in my experience) way this message occurs is when the VMSmail
recipient has their mail forwarded. Even if they have a valid forwarding
address, there seem to be occasions when MRGATE / VMSmail / whatever can't cope,
(ie can't find the forwarding address) and bounce the message.
Scott
|
| Caroline,
This is one of those "let's just put in a generic message and then put
better ones in a later baselevel" cases except the message has survived
5 ALL-IN-1 releases and about 8 years.
It is signalled by the AMTS (Alternate Mail Transport system) code
within the sender/Fetcher on almost every occassion where there is
a problem when executing the MAIL SEND line within SPECIAL.COM,
vAXMAIL.COM, VMSMAIL.COM or even a customer written one.
Cases where it happens can include:
invalid forwarding address (as scott mentioned)
but also remote node not reachable,
no MAIL object on remote node,
mailbox not reachable (when forwarding mail via A1 or MRGATE)
more ...
There's not a lot that can be done to change the POSTMASTER
non-deliveries without a good overhaul of the Sender/Fetcher
unfortunately...
personally I think this particularly error message isn't quite
as obscure as say "no actionable recipients" but i'm weird that way.
Regards,
Andrew.D.Wicks
|