Troubleshooting email
Use these techniques to troubleshoot email issues.
If you don't see your particular issue listed here, you may want to check out FAQ: Configuring and Troubleshooting Email Integration on Worx.
Appended email content being included
You may notice that Jive includes content appended to your emails, such as confidentiality notices or signatures. You can set Jive to ignore this content by adding five hyphens or underscores ("-----" or "_____") to the beginning of the appended content template in your email application. Jive excludes anything following five hyphens or underscores.
Automated reply emails causing stream pollution
If a user sets up an automated reply, such as an Out of the Office response, in their email client, your community may experience a wave of email content generated by these automated replies.
We strongly recommend using a Bounce Email Address. You can set this in the Admin Console at Configuring outgoing (SMTP) email.
. Automatic email replies are sent to the Bounce Email Address. For more information, seeEmail digests
By default, email digests are sent at 9:00 AM PST on Thursdays. Users can select in their Preferences to receive emails daily, semi-weekly, weekly, or never; the default is weekly. Users receive the digest email at the configured time in their timezone. If a user has not explicitly set timezone in their Preferences, the application server's timezone is used.
Out of Memory Errors can occur when the email manager has an
unlimited in-memory queue of email messages. Under normal conditions, the
application does not generate enough emails fast enough to encounter this situation.
However, in large communities, email can be generated so quickly that creating a
digest of all of them can overwhelm the application's email manager. The ideal
solution is to make the email manager's queue persistent so that it can handle any
number of messages without storing them all in memory. To avoid this problem, you
can adjust the jive.digest.batchSize
system property to include a
smaller number of email messages.
Users are not getting stream notifications via email
- Have users correctly configured their email notifications? For more information, see Choosing between email and stream notifications in the User Guide.
- Does at least one server in the cluster think it is the senior cluster member? The senior member is the node that starts up first in the cluster. For more information, see Clustering in Jive.
- Are emails actually being sent from the instance? To find out, check the destination SMTP server logs by turning on mail debugging on Configuring outgoing (SMTP) email. so that logs are written. For more details, see
- Send a test email to see if the SMTP server connection is working and that your outbound emails are not getting marked as spam somewhere upstream. You can do this in the Admin Console at Send Test Email button. by using the