Technical article 112321

MMDF mail sent to SCO OpenServer 5.0.5 results in return mail with rmail errors.

OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

Using MMDF over the UUCP channel to send mail to other systems running SCO OpenServer 5.0.5 results in the sender being sent a return message that may contain the following errors:

remote execution [uucp job # (date)]
rmail <uid>
exited with status 99
===== stderr was =====
rmail: mm_rrply at end of message.
or:
remote execution [uucp job # (date)]
rmail <uid>
exited with status 141

Cause

This problem is caused by a timing issue in rmail.

Solution

Setting the mmdftailor logging level to FTR prevents the problem, but is not a desirable solution since it creates large log files that can fill up the root filesystem.

Currently, the best solution is to use the following shell script to replace /usr/bin/rmail:

#!/bin/ksh
tmpfile=/tmp/rmail.$$
/bin/cat > $tmpfile
/usr/bin/rmail.bin "$@" < $tmpfile
ret=$?
/bin/rm -f -- $tmpfile
exit $ret

Move /usr/bin/rmail to /usr/bin/rmail.bin, and then create a new /usr/bin/rmail containing this shell script. Change its permissions to rwxr-xr-x (chmod 755).

NOTES:    This change should have an insignificant effect on the performance
          of MMDF and the system in general.

From the Xinuos technical article database, record 112321. Reproduced with permission. The original is at www.sco.com/ta/112321, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.