[ Main Index | IPSentry Help Index ]
 

From the Pager Alert Tab select Add or Modify pager, select Email/SMTP as the destination type.

Email Based SMS/Mobile Device Notification Configuration
Use the email based SMS/Mobile Device Notification to send emails via SMS to your cell or other mobile device or to your mailbox for forwarding to your Blackberry or other PDA.

IPSentry SMS Alert via SMTP (email to cell)

Max Length
Some mobile services limit the size of a message that can be sent to a mobile device. Due to the fact that a message that exceeds this length may be rejected by the services SMS system, IPSentry first truncates the message to insure that at least the first (n) characters are sent on the alert. It is better to receive part of a failure alert than no alert at all. Again, check with your paging service to verify the maximum message length that they will transmit. 

We recommend keeping the messages in this area brief with the most important information contained in the first part of the message.

Note: This is also useful for services that charge a fee for long messages allowing you to limit costs by keeping messages under this limit.

Force Uppercase
Checking this option will cause the entire message to be converted to upper case. Some SMS systems have been found to convert lowercase values to special characters or simply ignore them completely. This setting provides you with the workaround as well as a means to send messages to mobile devices that only support upper case letters.

The settings outlined below are common to all of the IPSentry outbound email configuration dialogues including Email Alert, Pager (SMTP) Alert, and the Email Transaction Monitoring Add-In.

Mail Server
Enter the IP Address of the SMTP Relay server that should be used to route the email message to the final recipient. The SMTP Server must accept SMTP email.

If you require MAPI delivery (Exchange Server), you will need to enter the MAPI declaration followed by the profile name used to send email.

For example, start Control Panel and select Mail.
Select Show Profiles to view or add an exchange profile.
The name given to the profile should be used here as follows:
MAPI:ProfileName
 

If the SMTP Server has any Anti-Spam features enabled that disable email based on this configuration, the alert will never be delivered and an error will be logged.  Some common errors that you will receive if Anti-Spam or Anti-Relay restrictions are disallowing mail will be in the 5.xx number range.

Errors such as "Relaying Prohibited" will suggest that you contact the mail server administrator to insure that your IP Address, From Address, To Address, and any other information specific to your network are set to allow SMTP email from the IPSentry machine as configured here.

One way around anti-relay (or if you don't know your relay server) is to send mail directly to the mail exchanger of the recipient email address.  You can obtain the mail exchanger address using NSLOOKUP -q=MX domain.name (where domain name is the domain of the TO address) - for example, nslookup -q=MX ipsentry.com

Backup / Redundant SMTP Server Configuration
IPSentry provides the means necessary to attempt delivery of email through multiple SMTP Relay servers to avoid situations where one or more relay servers may be unavailable when the alert is triggered. Simply enter the IP Address of each mail server that IPSentry should try in the order delivery should be attempted, separated by semi-colon.

(example: 10.1.1.1; 10.32.32.2; 10.27.33.3 ...)

In the event the first server is unavailable, IPSentry will attempt to deliver the message through the next relay host. IPSentry will attempt each host until the email is successfully accepted for delivery or until the list has been exhausted.

Note: Redundant SMTP Server option is not available when using MAPI / Exchange.

SSL / TLS - Authentication
You may specify to use an SSL or STARTTLS option by prefixing your mail server entry with <TLS> or <SSL>.  Normally, you will require this setting if your mail relay is secured and requires secured authentication.  The default port for SMTP relay for secured logon is 465.
 

Port
This field signifies the TCP port on which IPSentry should connect in order to deliver the message. By default, this field is set to 25 (SMTP), however, some internal SMTP servers may be setup on non-standard ports which will require that this field be changed to match the listening port of the mail exchanger.

Note: This option is not used when using MAPI / Exchange..

User
When sending mail through an Authenticated SMTP server, you can fill in the User and Password fields appropriately. If you are not using a secure SMTP server, an error 5xx "unrecognized" command may be returned from the server if you enter anything into one of these fields.  Note that the authentication method used is the standard SMTP AUTH and does not utilize Kerberos, NTLM, or SSL.  If encryption is required for the relay, you may want to look at sending directly to the mail exchanger for the recipient domain or if using exchange server, utilizing the MAPI method of sending email.

Note: This option is not used when using MAPI / Exchange..

Password
When sending mail through an Authenticated SMTP server, you can fill in the User and Password fields appropriately. If you are not using a secure SMTP server, an error 5xx unrecognized command may be returned from the server if you enter anything into one of these fields.

From
Enter the email address to be used as the FROM address in the email message. This field must be in standard name@domain.dom address format unless your relay server is prepared to accepted 'default domain' from addresses.

Most problems involving configuration of the Email alert are due primarily to an invalid email address format specified in the FROM/TO fields.  Specifically, send email to "SOMENAME" rather than "SOMENAME@SOMEDOMAIN.DOM".

Note: This option is not used when using MAPI / Exchange - instead, the profiles account address is used.

To
Enter the email address of the recipient (or recipients) of the email message. This field must be in standard name@domain.com address format unless your relay server is prepared to accepted 'default domain' from addresses.


Multiple Recipients
You may specify multiple recipients by simply separating the email addresses with a comma ",".
e.g.: me@here.com, you@there.com, somebody@somewhere.com


BCC Directive
In some cases (especially when monitoring your customer sites), you may want several internal messages to be delivered along with a message to the customer. In this case, you may not want the customer to see the address of the internal support staff, so a BCC (Blind Carbon Copy) can be utilized.

To accomplish this, simply precede the address list with "BCC:". This will cause IPSentry to send a unique email to each recipient in the list without including the actual recipient list in the "TO" line of the received message.
e.g.: BCC:me@here.com, you@there.com, somebody@somewhere.com

Most problems involving configuration of the Email alert are due primarily to an invalid email address format specified in the FROM/TO fields.  Specifically, send email to "SOMENAME" rather than "SOMENAME@SOMEDOMAIN.DOM".
 

Subject
The contents of this field will be placed in the subject field of the email message. All IPSentry keywords used in this field will be translated before the message is sent allowing you to specify crucial information in the subject of the message as well as the message text itself as it relates to the entry and the status of the entry..

Remember, when Alert Success is checked for this alert, the status keywords will be replaced by the actual status in verbose format depending on the state of the device. Use of status keywords in the subject is highly desired for obvious reasons.

Message
.Enter the message you wish to send when this alert is triggered. All IPSentry Keywords used in this field will be translated.

Special Headers
In some cases, you may want to insert special header information into the email message which may trigger special actions upon receipt of these alerts (either by the mail client software or within the mail processing cycle itself).

In order to specify special headers, you would make use of the "<HEADER:..." directive at the top of the message text.

Syntax: <HEADER:HeaderName: VALUE>
Use of this directive would cause an email header "HeaderName" with the value of "VALUE" to be inserted into the headers of the email message before the message is sent to the server.

For instance, if you wanted to set Importance to HIGH and Priority to 1 to insure that special attention was given to these email messages, you might use the following directives:
<HEADER:X-Priority: 1>
<HEADER:Importance: high>

IPSentry expects NOTHING ELSE on a HEADER line.
Also note: You can use the IPSentry keywords in the header fields as replacement values. Be careful not to use a value with a new line character...

Note: Special headers are not used for MAPI delivery.

 



     If you require additional assistance, please visit our on-line support forum at http://forum.ipsentry.com.
 
©1997-2012 by RGE, Inc. - All Rights Reserved
IPSentry® is a registered trademark of RGE, Inc.

 
Support Forums: http://forum.ipsentry.com
Web Site: http://www.ipsentry.com
Support Email: support@ipsentry.com