E-mail client – System Sensor FAAST Networking User Manual
Page 31
![background image](/manuals/352663/31/background.png)
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Networking
31
E-mail Client
One of the exciting features offered by the FAAST aspiration smoke detector is the ability to generate e-mail notifications of alarm and
fault conditions. With this technology, users may be alerted to changes in the system whenever and wherever they are.
Features
The 8100 series is equipped with an integrated SMTP client capable of forwarding alarm and fault e-mail notifications to a properly
configured SMTP mail server. In addition, the detector has DNS name resolution capability for locating a mail server inside a LAN.
Configurable features of the SMTP client include:
• The name of the SMTP server used for relaying messages
• The sender e-mail account used for relaying messages
• Up to 6 unique e-mail recipients
• An independent collection of alarm and fault notifications for each e-mail recipient
The integrated SMTP client is configured using the PipeIQ software.
Network Requirements
Before the integrated client can forward messages to the mail server, it must be able to make a connection to it. For this to occur, the
following are required:
• The detector must be connected to a TCP/IP network via Ethernet and have a properly assigned IP address. Dynamic IP ad-
dress assignment via DHCP is supported; however, for permanent installations, static IP addressing is recommended.
• The detector must be configured to forward messages to the machine where the SMTP server resides. The mail server must be
specified by its hostname. Specifying the IP address of the mail server directly is not supported. If the mail server and detector
are not part of the same domain, the FQDN (fully qualified domain name) should be specified.
• In order for the FAAST detector to connect to the mail server, it must be able to resolve the hostname. This is accomplished
using DNS. For proper operation, the Primary and/or Secondary DNS servers the device will use for name resolution must be
configured. The device will query these servers when attempting to resolve the name of the mail server. The DNS servers must
be capable of resolving the name of the mail server or petitioning other DNS servers that can.