Inbound Gateway Service
The AppSettings.Config file for the Inbound Gateway service defines the app settings for this service. It contains the following application settings.
Setting | Description |
---|---|
ExchangeVersion
|
Defines the Microsoft Exchange version, for example Exchange2010 . |
EmailServerConnString
|
Defines the string for your email server connection. |
FetchTimeSeconds
|
Defines how frequently to check mailboxes. For the value, enter a number for the time interval, in seconds, for example, 3. |
ReadInboxMessageFolder
|
Possible values are If set to If set to |
AllowedExt
|
Defines the file name extensions that are allowed for customer email attachments. Type a comma-separated list. For example:
Note: If a customer attaches a file with a file name extension that is not included in this list, the email message is added to a new record in INTERACTION_X_MESSAGE but the attachment is not saved. For such a record, Syntelate XA sets LKTL_FILESTRIP to Y. |
AsyncExchangeAccess
|
Defines whether mailboxes are polled asynchronously. Possible values are Note: We recommend that this setting is set to |
ErrorEmailTo
|
Defines the email address to which the daily error log report should be sent. |
ErrorEmailTime
|
Defines the time at which the daily error log report email should be sent. Enter the time in the format hh:mm , using the 24-hour clock. For example, to send the email just before midnight, enter 23:59 . |
ErrorEmailActive
|
Defines whether the daily error log report email should be sent. Possible values are true and false . |
ErrorLogToSend
|
Defines the full path of the log file to attach to the daily error log report email. |
ErrorEmailSubject
|
Defines the subject of the daily error log report email. |
ErrorEmailBody
|
Defines the body text of the daily error log report email. Type
|
MaxAutoRepliesPerEmailAddressIn24Hrs
|
Limits the number of auto-reply emails sent to the same email address. We recommend setting this value to “3”. |
MaxAutoRepliesPerInteractionIn24Hrs
|
Limits the number of auto-reply emails sent to the same interaction record. We recommend setting this value to “3”. |
MaxRetries
|
Specifies the maximum number of receive attempts accepted before new inbound messages are ignored. We recommend setting this value to “2”. This setting is also used by the outbound gateway for send attempts; both gateways need to be set to the same value, which should be “2”. |
sqlConnectionString
|
Required. Defines the SQL server connection string. For web chat, remember to also specify the |
ChatUrl
|
Required for web chat. Defines the URL of your Message Host web application. Remember to also specify the |
ChatConnectRetryIntervalSeconds
|
Defines the number of seconds to wait before attempting to reconnect if a web chat connection is lost. |
SmsUrl
|
Required for SMS chat (but not outbound SMS). Defines the URL of your SMS API. |
MailRefreshMins
|
Defines how frequently, in minutes, the Inbound Gateway service should check for new email rules. Email rules are defined in database table IMMAILBOXRULES. They can be managed via a configuration desktop. See |
NewContactCreateAlways
|
Valid values: one or more email addresses. Wildcards may be used, such as an asterisk. You need to separate multiple email addresses by three pipe symbols. For example:
Defines whether to always create a new record in the CONTACT_X table for inbound emails, even if a contact already exists for the email address. If the value for |
IgnoreConversationIdAllContacts
|
Valid values: true | false For inbound email from either a new or an existing contact, this setting determines if the email will be chained to an existing email that has the same conversation ID and associated with the same interaction record. If set to true, then an inbound email will not be chained to an existing email. If set to false, then the inbound email will be chained to an existing email that has the same conversation ID and will be associated with the same interaction record as the existing email. |
IgnoreConversationIdNewContacts
|
Valid values: true | false For inbound email from newly created contacts, this setting determines if the email will be chained to an existing email that has the same conversation ID and associated with the same interaction record. We recommend specifying this setting to true. If set to true, then an inbound email from a newly created contact will not be chained to an existing conversation and therefore will not be associated with an existing interaction record. If set to false, then the inbound email will be chained to an existing email that has the same conversation ID and will be associated with the same interaction record as the existing email. |