Introduction

EuroRunner can send notices by e-mail, but it does not support the ability to automatically receive e-mail notices, e-mail notices received by an operator must be manually saved into the EuroRunner Inbox, so the notice can be processed.

Set-Up

Both Transit Notices (to a network operator) and Contract notices (to any other counterparty) can be sent by e-mail.

Configuration

To set-up EuroRunner to allow sending of notices by e-mail; set the following properties for any of Network, Network Group, Contract or Contract Group:

1. This option enables sending of notices.
   Note: The caption This Network can send Notices will be different on the Network Group, Contract and Contract Group notice properties.
2. Choose the interface with which EuroRunner will interact: E-Mail
3. List of formats in which to send the notice: HTML or Text
4. E-mail address of notice recipient. Multiple e-mail addresses can be entered separated by semi-colons (;).
5. Provides an alternative easy to read view of the notice data.

Then set-up specific templates for the notices to be sent/viewed as using the properties for any of Flange, Point, Journey, Network, Network Group, Contract or Contract Group:

1. Checking this allows daily notices to be sent.
2. This allows the user to choose a specific template for the notice be transformed into when being sent.
3. This allows the user to choose a specific template for the notice to be transformed into when being viewed by the user.

Note: Template selections will depend on object type, there may be custom templates available, you should know when you need to use these rather than the default templates.

Technical

EuroRunner utilizes Microsoft’s CDO component to send e-mails from within EuroRunner without having to interface with any e-mail clients such as Lotus Notes, MS Outlook etc. instead EuroRunner connects directly with your network's SMTP server.

As the notices are being sent via e-mail, once the e-mail has left the system there is no way for EuroRunner to know if the message has failed or succeeded, so it assumes success.

EuroRunner will only notify the user of a problem with an e-mail message if the problem is regarding a set-up issue preventing the e-mail to actually be sent i.e. incorrect SMTP server.

Problems such as incorrect recipient/sender e-mail addresses cannot be handled by EuroRunner and will be handled by usual the e-mail standards e.g. Bounced e-mails etc.

Configuration

During the installation of EuroRunner the SMTP server and the sender e-mail address are required to be entered, these are stored in the registry (see the E-Mail section of the Registry documentation).

The SMTP server can either be the IP address of your SMTP server e.g. 192.168.1.2, or it can be the hostname of the SMTP server e.g. smtp.companydomain.co.uk.

The sender e-mail address is the e-mail address that the e-mail will appear to have come from and is also the e-mail address that any bounced e-mails will be delivered to.

SMTP is a simple networking protocol that uses a standard port number of 25; some system administrators change this port number to a different port number for a variety of different reasons. Because of this the SMTP port number that EuroRunner connects to can also be altered to match the servers SMTP port number, this is only configurable via the registry (see the E-Mail section of the Registry documentation).

Troubleshooting

E-mails are returned (bounced) back to my sender e-mail address:

• Ensure that the recipient e-mail address is correct.
• E-mails that have bounced back have information in them to help diagnose the reason for the e-mail failing to be delivered i.e. unknown mailbox, mailbox full etc.

Notice is not being sent successfully:

• Ensure that the SMTP server address/hostname entered is correct and is accessible from the application server. To check this, open a windows command prompt and type telnet [smtpserver] 25.
  For instance, if your SMTP server was 192.168.1.2 you would type telnet 192.168.1.2 25.
• When you run this command you should see a response such as 220 ESMTP 1.1 or something similar.
• If you see this then your application server is able to connect to the server and is not the cause of the notice failure.
• If you see Connect Failed in the command prompt window then your application server either cannot connect to the SMTP server because of permissions i.e. Firewall etc. or you have entered the wrong SMTP address/hostname.

Notices are not being received by the recipient:

• Because of the nature of the Internet, e-mails can still take some time to be received by the recipient. This can be caused by a number of things including e-mail forwarders, mail queues, high level of traffic, incorrect recipient e-mail address etc.

Registry Keys

See the E-Mail section of the Registry documentation.