Email Alarms - SMTP

Have more questions? Submit a request

Email Alarms - SMTP

Options

There are 2 ways to send SMTP alerts in to Ops from a security device or system:

  1. Via a real email server, in which case the email path will look like this: Source system/device -> real SMTP server -> Ops
  2. Directly to the Ops servers, so the email path looks like this: Source system/device -> Ops

IMPORTANT: Whichever option you choose, you must test that your settings work otherwise you may not receive alarms. Guidance on doing this is provided below.

IMPORTANT: Changes to the settings of the security device/system may stop it sending alarms to you - where possible you should limit the number of people who have access to change settings on the security devices and systems.

1) Real email via an email server

To send real email via an email server you will need to:

  1. Have the device/system configured according to the manufacturer's instructions, enabling it to send emails out to real email addresses.
  2. Enter the email address provided by the Ops "Alarm Setup" screen for it to be sent to.

2) Direct to Ops

To send email direct from a system or device you will need to:

  1. Edit the SMTP Server settings of the device/system by following the manufacturer's instructions to set the following: (Refer to your manufacturer's instructions to find where these are located)
    1. SMTP Server:
      1. smtp-us.sureviewops.com (if your Ops account is held in the US environment)
      2. smtp-eu.sureviewops.com (if your Ops account is held in the EU environment)
    2. SMTP Port: 587 (port 25 is also supported but many ISPs block this outgoing as it is meant for mail server-to-mail server communication only)
    3. Encryption: STARTTLS is supported if you wish to encrypt the messages from your system to Ops (sometimes listed as "TLS").
    4. Authentication: None necessary (the address being sent to is used to identify the device)
    5. Sender name/address: Any value (this will be shown in the email viewer of the Ops interface so you may wish to use it to identify the source device/system)
    6. Attachments: have the system include any images, video, or other attachments as necessary (these will be shown in the email viewer in the Ops interface).
  2. To address: The email address provided by the Ops "Alarm Setup" screen must be entered as the "To" address for your system to send its emails to.

Testing Guidance

There are a number of ways you can test email sending:

1) Test the address using a online email service

Use an email service such as GMail to send an email to the address provided by Ops - shortly after sending you should see it appear as an alarm in the queue. This tells you that Ops is working to receive email to that address.

2) Test your SMTP server details using a SMTP tester

You can check your details work using a SMTP tester.

NOTE: You should test sending to your own email address to completely rule out Ops - if you do not receive anything in your inbox then there is a problem with your SMTP details.

To do this you can use:

Example using PowerShell to send directly to the Ops server (replace the values if you are using your own SMTP server details or sending to your own email inbox):

Send-MailMessage -ComputerName smtp-YourEnvironment.sureviewops.com -Port 587 -From anything@anything.com -To AddressProvided@OpsUI.com -Subject "Some subject to appear in the alert line" -Body "Some body to appear in the viewer"

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.