A remote workstation does not initialize after JnextPlan

After running JnextPlan you notice that a remote workstation does not immediately initialize. The following message is seen: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ AWSBCW037E  Writer cannot initialize this workstation because mailman 
+ is still active.
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ AWSBCW039E Writer encountered an error opening the Mailbox.msg file. 
+ The total cpu time used is as follows:  0 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Cause and solution:

If mailman is still running a process on the remote workstation, JnextPlan cannot download the Symphony file and initialize the next production period's activities. Instead, the domain manager issues a stop command to the workstation. The workstation reacts in the normal way to the stop command, completing those activities it must complete and stopping those activities it can stop.

After the interval determined in the localopts parameter mm retrylink, the domain manager tries again to initialize the workstation. When it finds that the stop command has been implemented, it starts to initialize the workstation, downloading the Symphony file and starting the workstation's activities.