Setting up email
Jive can send email to users on various occasions. For example, email notifications can be sent about stream updates and as welcome messages. Also, Jive can receive email from users to create new content or to reply to existing content. For example, a user can create discussions and blog posts in the application directly from the email. You can choose how email is used and customize the email templates.
- Getting set up with email Here are some things to be aware of when setting up your community's email services.
Using user email addresses
One of the requirements in Jive communities is that users must have unique email addresses. This allows users' email addresses to be used as usernames within communities. Despite that, we recommend that you do not set Jive usernames to be the email addresses of users. If you do this, the user's email address string will show up in the user's profile page URL, even if email visibility is set to Private To User. If you are using SSO for authentication, you should set it to authenticate each user's username.
- How incoming and outgoing email works Jive communities can both send emails to users and receive emails from users.
Configuring outgoing SMTP email server
Jive uses an outgoing SMTP email server for sending messages, such as content update notifications, task reminders, and registration confirmations. You configure a connection to the server in the Admin Console or by using the Setup wizard.
Configuring incoming email server for creating content via email
You can enable features through which people can post content to the application by sending email to a particular address. For that, you should set the connection to an incoming email server so the instance can receive email messages from users.
Disabling email in test environments
In test environments, disabling email prevents the test instance from sending email updates to your users. Your production instance is typically set up to both send email notifications (SMTP) and access an email account (Email Monitor) or server (Advanced Incoming Email). In your test production instance, you can temporarily change these settings; otherwise, you may find that the new test instance generates email notifications that look like they're coming from your production instance, which can confuse users and unnecessarily burden your email servers.
Configuring email digests
You can customize your digest email settings for your community.
Editing and localizing email templates
Jive includes a set of email templates for emails it sends to users in response to certain events. You may want to edit the default email notification templates to perform content changes or to include password reset notifications.
Preventing email spam
You can use a variety of best practices to avoid spam in your community. Here are some general spam prevention strategies, as well as those that target specific spammers.