This feature is available in Catalyst, Enterprise, and Ultimate editions.
If the SMTP settings are not configured, member email preferences will be ignored.
Recommended Setup for On-Demand (V1 Hosted) Installations
We recommend running Microsoft's SMTP Service on the same machine hosting your Lifecycle application when running an on-premise system. This reduces the risk of failure when delivering a message to the first SMTP server. If you use this option, you only need to enable SMTP and provide information for the required fields. If not, you will need to provide the optional parameters necessary to connect to your SMTP server. This information is available from your network administrator.
Step 1. Configure SMTP Settings
Select Admin > Configuration > SMTP.
Enter the appropriate information in the following fields, and then click Save.
The name used by the application when sending messages; this will show up in the recipients' email as the From field
Send All Emails As System
Use this option if your corporate email security settings disallow emails from internal users to originate from outside your domain, blocking messages from your On-Demand (V1 Hosted) instance.
Email address used by the application when sending messages
Name of machine hosting the SMTP Server
SMTP Server listen port
Select this option if the SMTP connection is secure (aka SSL or TSL)
The user name part of authentication to the SMTP server
The password part of authentication to the SMTP server
* These fields may be required by your SMTP server.
If you are a hosted customer, the "From Name" and "From Address" fields are the only options available. These fields are set by default during installation and should not be changed.
Step 2. Testing SMTP Settings
To confirm that the SMTP configuration works correctly in your environment, you can test your settings.
Type an email address in the Send Test Email To field.
Click the Save a Test Email button.
Note that the system will not generate any automatic notifications to a member for actions that user takes themselves. For example, if a member has a subscription to generate a notification when the user is assigned a defect and the user creates and assigns a defect to his/herself, the system will not generate a notification (as it assumes that members are already aware of the actions they take themselves).