The Helix Platform Common Services installation script (deployment-manager.sh) requires an SMTP server to be available during the preinstall stage and to be used to deliver the Helix Platform tenant activation message.  If a full time SMTP server is not available there are several alternative options such as those below.

PLEASE NOTE - this process is suitable for test systems only and is not intended for production environments where a working SMTP is required for full product functionality.

Fake SMTP servers can be run on a local workstation and will accept and store the messages sent during the installation process.  Examples include;

https://mailcatcher.me
http://nilhcem.com/FakeSMTP
https://github.com/gessnerfl/fake-smtp-server

There are also Docker based versions of the above which make deployment and use very straightforward.  For example;

https://hub.docker.com/r/dockage/mailcatcher

Another option is the smtp-sink command which is part of the popular postfix package on Linux.  smtp-sink can be configured to accept SMTP traffic on any available port and save messages to files for later review.  The messages sent by the installer are in HTML format and so this method requires more work to decode the account activation link that is included in the message.

In this example the command is being run on the BMC Deployment Engine (CentOS based) that is used to install the Helix Innovation Suite packages.

The SMTP server host and port are set in the infra.config file with these variables;

SMTP_HOST=testpc.bmc.com
SMTP_PORT=2525

At the command prompt on the host being used make sure that packages needed are installed;

# yum -y install postfix tokyocabinet

Find the IP address of the system where smtp-sink is being run;

# ip route get 1 | awk '{print $NF;exit}'
172.20.100.1

Run smtp-sink in the background, listen on port 25 and save messages to files;

# smtp-sink -u root -d -c 172.20.100.1:2525 100&

Now you can run the deployment-manager script and it will confirm SMTP connectivity during the pre-install checks and show this on the console;

[220421-045623] INFO: Checking SMTP server connectivity
[220421-045639] INFO: Connectivity to SMTP server testpc.bmc.com has been verified

As the script finishes it will send an email which will be saved as a file in the directory that smtp-sink was run from.  The name of the file starts with a hyphen character and it contains the email in quoted-printable format. In this example the name of the file is -c259cec3b

# ls -l
total 72
-rw-------. 1 root root  1583 Sep 22  2015 anaconda-ks.cfg
-rw-r--r--  1 root root 18389 Apr 21 09:32 -c259cec3b
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Desktop
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Documents
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Downloads
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Music
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Pictures
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Public
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Templates
drwxr-xr-x. 2 root root  4096 Sep 22  2015 Videos

Use one of the tools installed earlier to decode the file and show the registration URL;

# tcucodec quote -d ./-c259cec3b |  grep confirm-registration | sed -e 's/.*href="//g;s/".*//g' -e 's/=/=/g'
https://customer-private-poc.cluster.company.com/rsso/action/confirm-registration?id=a6d2c1c6-9f4a-403a-bbf4-3ed0981ddffd

Copy the link into a browser and you should be taken to the RSSO change password page.  Don't forget to kill the smtp-sink process once you're finished.