Email Setup on LTK3607FM-T

Using the latest firmware release, LTK3607FM-T can send email notifications directly from the terminal, eliminating the dependency on client software for such feature. This document will guide through the necessary pre-requisites and procedures required to setup email notifications on LTK3607FM-T.

Device Access to Email Service

Certain email services, such as Gmail, may prevent devices or software from accessing its email features by default. In most cases, the email account must be set to allow “less secure apps” for LTK3607FM-T to utilize the account for email notifications during an event trigger. The example below describes how to configure this on a Gmail account.

1. Login to Gmail and enter the account settings by selecting the user icon at the top right and clicking on [Manage your Google Account].

2. Go to [Security] and find the [Less secure app access] section of the page. Enable access to this feature. It may take minutes for this setting to take effect.

Event History and Email Notifications

All event data currently stored in LTK3607FM-T will be treated as queued notifications when the email feature is enabled, which may cause numerous emails to be sent at one time. It is highly recommended that event data is backed up and then erased from LTK3607FM-T to prevent this. Event data can be exported locally with a USB storage device or remotely via iVMS-4200 client software. Please refer to the document, Export Event Data from LTK3607FM-T, for more information.

LTK3607FM-T Email Setup

Email feature of LTK3607FM-T can only be setup and configured through its local interface. Please ensure that the email account credentials, and the terminal’s administrator password is known before proceeding.

1. In the default screen of LTK3607FM-T, hold the screen for several seconds until the terminal prompts for an administrator password. Enter the terminal’s administrator password to enter the settings menu.

2. Go to the [Mail] menu section to setup and configure email notifications. All email account and recipient information will be entered in this menu. Please note that email notifications are limited to only one recipient.

		Sender:	Sender’s name on the email message.
		Sender’s Address:	Sender’s email address on the email message.
		SMTP Server:	SMTP server address of email service. (e.g. smtp.gmail.com for Gmail)
		SMTP Port:	SMTP port used by the SMTP server. The port should correspond to the encryption chosen. (e.g. 587 for Gmail TLS encryption)
		User Name:	Username of email account; enter full email address. (e.g. [e-mail])
		Password:	Password of email account.
		Confirm Password:	Confirm password of email account.
		Receiver:	Name of email recipient.
		Receiver’s Address:	Email address of recipient.
		Authentication:	Required for terminal to send authentication to email server. Ensure that this is enabled.
		Enable email:	Enable email notification feature.
		Encryption:	Encryption used by SMTP server. (e.g. TLS for Gmail)

3. Save setup and configuration changes by pressing on the [ √ ] icon at the top right of the menu. Email notifications will now be sent based on abnormal temperature and no mask detection events. Below are examples of the email notifications sent by LTK3607FM-T.

LTK3607FM-T Event Email Setup on iVMS-4200

Notification emails can also be sent through the iVMS-4200 starting from version 3.3.1.8.  Steps below:

1. Setup email sender and receiver information iVMS-4200.
2. Perform a Test Email to ensure client and network settings are correct.
3. Choose the appropriate event to trigger sending a notification emails.  v3.3.1.8 sends only a thermal photo as email attachment.

Note: There is a current issue with iVMS-4200 v3.3.1.8 that a test email along with other common triggering events will send emails, but not "Abnormal Temperature" event.  This will be corrected in the next v3.4 formal release.  Before that is available, can replace iVMS-4200.AlarmCenter.C file with the attached as a temporary solution.  Need to close iVMS-4200 client completely first including service before file replacement is made.