Relay Emails through SMTP gateway with authentication

You can set up TeamForge to relay emails through an SMTP gateway (such as Amazon AES) that uses authentication. By default, James sends emails directly. However, you may prefer relaying emails through an enterprise relay server. Configuring the following James tokens let you do that.

JAMES_GATEWAY_HOST and JAMES_GATEWAY_PORT specify the relay server's FQDN and port to use respectively. The JAMES_GATEWAY_HOST token specifies a mail server with Internet access, separate from the TeamForge Application Server. Specify the gateway host by its fully qualified domain name (FQDN), not a host name.
JAMES_GATEWAY_USERNAME and JAMES_GATEWAY_PASSWORD specify the relay server credentials. These tokens are optional that should only be used if the relay server requires SMTP authentication.

Important: By default, TeamForge uses the user's email address (as registred in TeamForge user profile) as the sender address ("From"). Therefore, it is important that the mail relay does not impose any restrictions on the email sender address and accepts all emails to be relayed.

To relay emails through SMTP gateway:

Set the following site-options.conf tokens.
- vi /opt/collabnet/teamforge/etc/site-options.conf
```
JAMES_GATEWAY_HOST=
JAMES_GATEWAY_PORT=
JAMES_GATEWAY_USERNAME=
JAMES_GATEWAY_PASSWORD=
```
Save the site-options.conf file.
Provision services.
- /opt/collabnet/teamforge/bin/teamforge provision