Google
 

Trailing-Edge - PDP-10 Archives - BB-BT99V-BB_1990 - 10,7/decmai/mx/readme.txt
There are 15 other files named readme.txt in the archive. Click here to see a list.
   MX will now forward mail if you have a forwarding address set up
   via REACT.  For example, if your forwarding address is JSMITH@NODE,
   MX will not deliver mail to you locally but will forward it to
   JSMITH at NODE.

                          Known bugs and deficiencies:

   Be careful setting up forwarding addresses.  There is no loop
   detection.  So, user A forwards to user B, who forwards to user
   A... will cause lots of confusion.

   Other errors in forwarding are handled in one of two ways:

   If the error is noticed before the message is requeued (for
   example, the user specified an invalid local recipient to forward
   to), a postmaster message is generated that states that an error
   was encountered while attempting to forward the message.  The
   sender should contact the recipient by other means so that the
   forwarding problem can be resolved.

   If the error is noticed after the message has been requeued (for
   example, the user specified an invalid remote recipient) then the
   mail is not delivered, and a postmaster message will be sent back
   to the original sender.  So, for example, you send mail to
   FOO::JSMITH.  You get back a postmaster message that says "No such
   user BJONES at node BAR". In this case it is merely confusing.  If,
   instead, one had sent to a large mailing list, it may be very
   difficult for the original sender to track down who the actual
   culprit was.  The system manager should be able track down who the
   actual culprit was.  The system manager should be able to figure
   out who tried to forward where by looking at UPS:MX.LOG on the
   system running MX.