Retention SMTP configuration settings

Version 1

    Below is an SMTP settings page for 6.0.2-5

    Jive Admin Console _ Email_SMTP - 2013-10-31_09.41.03.png

    Must change settings:

     

    SettingNotes
    retention.smtp.message.inbox.addressThis is the inbox where all retention messages will be sent. This should be an inbox that your archival systems will scan.
    retention.smtp.reply.to.addressNo one should "reply to" a retention email, so you can use the same value as "retention.smtp.message.inbox.address". Bounce messages will also go this address, so you can also set this to a "junk" email address.
    retention.smtp.envelope.sent.from.addressUsually, the value of "retention.smtp.message.inbox.address" may be used here. If retention messages are being rejected by your gateway, you may need to set this to an address which your gateway will accept.

     

    May change settings:

    These are settings that may be changed, depending on how your use cases. These are loosely in order of importance.

    SettingNotes
    retention.attachable.size.limitThis should be set to the same max size that Attachments, Images and Uploads are configured within Jive. This should be less than the maximum size your email gateway will accept.
    retention.deletes.processing.onSet this to "true" to capture delete events. Please note that delete records have very little information about the content that was deleted.
    retention.reaper.messagearchive.number.of.days.to.keepThe number of days which records will be retained. Once a record is sent, it is considered "done" by the retention module. However, records can be saved for a period of time so you can "replay" events. This setting refers to textual content.
    retention.reaper.capturedbinary.number.of.days.to.keepThe number of days which records will be retained. Once a record is sent, it is considered "done" by the retention module. However, records can be saved for a period of time so you can "replay" events. This setting refers to binaries, including attachments, images and uploaded files.
    retention.mail.smtp.server.overrideRetention will use the same email settings as the Jive server unless you set this value to "true". Once this value is set to true (make sure you save the settings), a number of other settings will appear, allowing you to configure the smtp server settings Retention should use.
    retention.max.cc.list.size.for.groups.and.spacesLimits the number of email addresses included with private or restricted content.
    retention.resolve.and.store.cclists.for.spacesSince collection of users with access to restricted content is expensive, this can be used to turn this feature off.
    retention.server.internalEmailDomainsThis ignores users whose email addresses is not found within the comma separate list of domains in this setting. This is useful for reducing the size of each email message, but does not prevent the expense of collecting user addresses on private or restricted content.

     

    No need to change settings:

    These are intended to address specific issues. In general, you don't need to change these unless you have a specific use case or problem you're trying to address.

    SettingNotes
    retention.delay.between.each.message.sentThis "throttles" the speed with which emails sent to your gateway, though their arrival is not guaranteed.
    retention.delay.processing.messageThis sets the amount of time records must remain in the queue before they are available for processing. This is mainly a legacy setting, but remains very useful for troubleshooting and diagnostics.
    retention.do.not.filter.duped.eventsThe Retention module is able to identify and filter multiple events for a single action. Setting this to true causes known duplicates to be ignored. Setting this to false will cause all known duplicates to be delivered.
    retention.max.cc.list.size.for.groups.and.spacesLimits the number of email addresses included with private or restricted content.
    retention.new.objects.considered.new.for.millisecondsSince Jive fires multiple events when creating some types of content, the Retention module will ignore edits that occur on newly created content. Because content created during very heavy traffic can cause the time period over which these events are fired, there is no way to completely eliminate "false edit" records, however this setting may help to limit them.
    retention.number.or.records.to.get.from.queueMaximum number of records to pull from the queue at a time. Usually only an issue when replaying records.
    retention.resolve.and.store.cclists.for.spacesSince collection of users with access to restricted content is expensive, this can be used to turn this feature off.
    retention.smtp.content.typeChanging this usually prevents unicode characters from being ingested into your archival system. You probably don't want to change this! You email administrator will tell you if this needs to be changed, along with the correct value to use.
    retention.smtp.xheader.name.mappingAllows changing the names of the X_HEADER values passed with each email message.