You are right, that was a typo on my part. Thanks for the correction.

uuencode and mailx are both standard UNIX utilities. They should reside in /bin or /usr/bin on most systems (btw.: care to tell us on which OS you are?) If you have /bin in your PATH (which you should have anyways) that means they are not installed. Get them installed in this case.

In general "executable: not found" can have three reasons and you will have to investigate them yourself because we can't look onto your system:

1) the executable is installed but not in the PATH:
If you have some program /foo/bar/program and you call it with

Code:

program

(that is: without the full path) you need to its respective path included in the PATH statement (actually this is what PATH is for), like this:

Code:

PATH="${PATH}:/foo/bar"

2) the executable is not installed at all
You obviously need to install it, in this case. To find out if it is installed you can run the following command (note that it might run for some while)

Code:

find / -type f -name "your_executable" -print 2>/dev/null

3) the executable is installed but filemodes are wrong
The operating system identifies (potentially) executable files by the filemode, i.e.:

Code:

# ls -l /bin/mailx
-rwxr-xr-x    3 bin      mail         159650 Jan 22 2016  /bin/mailx

The first "x" means that the owner of the file (bin) may execute it. The second "x" means that every member of the group "mail" is allowed to execute it. The third "x" means that every other user is also allowed to execute it.

What you see here for mailx is the default, but some security aficionados tamper with these filemodes and set it to

Code:

# ls -l /bin/mailx
----------    3 bin      mail         159650 Jan 22 2016  /bin/mailx

That means nobody is allowed to do anything (read, write or execute) with this file, not even its owner. It might be that someone deemed mailx or uuecode so dangerous that the only way to deal with this threat was to flag it that way. I have seen such things.

To make it work again you simply need (as root) to reinstate its original filemodes:

Code:

# chmod 755 /bin/mailx
# ls -l /bin/mailx
-rwxr-xr-x    3 bin      mail         159650 Jan 22 2016  /bin/mailx

I hope this helps.

bakunin