Many software modules send out alerts via e-mail. You can configure outbound mail settings to make sure these alerts get to you.
This module is automatically installed when another module requires mail alerts.
You can find this feature in the menu system at the following location:
The hostname of the SMTP server to connect to.
The port to used to send the initial connection request on. SMTP usually uses port 25.
Encryption protocol to use when connecting to the host server.
A valid username to authenticate to the server.
A valid password to authenticate to the server.
Once you have configured the mail settings, it is time to ensure e-mails can get through successfully:
If a successful connection and authentication (if required) is made, you will receive a notification that the test was successful. If the connection could not be made or if authentication using the settings provided failed, you need to go back and check your settings and then repeat the test.
You should also verify that receipt of the test e-mail that is sent to the address specified, especially in the cases where you are using localhost as the SMTP hostname. You may find the test is successful, but you never receive the test message. In this case, the message could be queued on the local server and unable to deliver - usually because an ISP is blocking SMTP traffic.
Local SMTP Server
If you are running a local ClearOS [SMTP Server]] on the same server, you can leave the default in place (for example, port 25 at localhost). Keep in mind, this assumes that your local mail server is either:
relaying directly and your ISP does not filter/block SMTP (port 25) traffic
relaying through your ISP's SMTP servers
configured to relay through an alternative (possibly non-standard port) relay service
Google Mail (Gmail)
With a valid Gmail account, one can easily set up the this module to relay through Google's SMTP server. Here is an example for a user with a Gmail account of “email@example.com”.