L o g   M a i l   N o t i f i c a t i o n

Contents

1. Introduction
2. System Requirements
3. Purchase and Licensing
4. Installation
5. Configuration
   • Recommended Procedure
   • Log File Monitoring
   • Query Interval
   • SMTP Function
   • Mail Recipients
   • Test Email Sending
   • General Contact
   • Activation / License
   • Specific Settings
   • Proxy Configuration
6. Usage
7. Troubleshooting
8. Updates
9. Support & Contact

 

Introduction

Log Mail Notification (LMN) is a Windows service for scheduled monitoring of log files. When defined keywords are detected in up to three log files, the system automatically sends email notifications. Configuration is flexible via an XML file. LMN supports both internal and custom SMTP servers for sending emails. The internal SMTP function is not included in the Ultimate version.

 

System Requirements

Operating System: Windows 11, Server 2019+
.NET Framework: 4.8 or higher
512 MB RAM

Internet:

• Required for SMTP, Port 465/587
• Required for license verification and activation, Port 443

Optional:

SMTP account with credentials (for custom email sending)

Note:

The Windows service Log Mail Notification requires appropriate permissions to access the monitored log files and is installed under the system context.

 

Purchase and Licensing

You can purchase Log Mail Notification with the appropriate license via our website: https://www.logmailnotification.com. You will also find tips for using the program there.

The license models are available for different usage scenarios, are valid for one year, and do not renew automatically. These are not subscriptions. Before a license expires, you will be notified by email and can decide whether to purchase a new license. For single licenses, computer activation can be released at any time in the customer area.

There is no upgrade function for our license models. If you have any licensing questions, please contact our support (see Support & Contact section).

License Models

Log Mail Notification – Trial

• License: 3 days
• Subscription: No
• Operating System: Windows
• Host System: Clients
• Computer: StandAlone
• Clients: 1
• Framework: .NET 4.8
• Mail SMTP: custom, included
• Updates: No
• Language: DE, EN

 

Log Mail Notification – Standard

• License: 1 year
• Subscription: No
• Operating System: Windows
• Host System: Clients
• Computer: StandAlone
• Clients: 1
• Framework: .NET 4.8
• Mail SMTP: custom, included
• Updates: Yes
• Language: DE, EN

 

Log Mail Notification – Professional

• License: 1 year
• Subscription: No
• Operating System: Windows
• Host System: Clients, Server
• Computer: StandAlone, Domain
• Clients: 1
• Framework: .NET 4.8
• Mail SMTP: custom, included
• Updates: Yes
• Language: DE, EN

 

Log Mail Notification – Ultimate

• License: 1 year
• Subscription: No
• Operating System: Windows
• Host System: Clients, Server
• Computer: StandAlone, Domain
• Clients: unlimited
• Framework: .NET 4.8
• Mail SMTP: custom
• Updates: Yes
• Language: DE, EN

 

Current license information for the program in use can be viewed at any time in the log messages of Log Mail Notification itself.

Installation

The installation of Log Mail Notification is simple and flexible. The setup supports both a graphical user interface (GUI) and a silent installation for automated deployments. Both variants offer the same functionality and are optimized for different usage scenarios. The installation file is available to you after purchasing Log Mail Notification in the customer area of our website.

Note:

For installations with an existing previous installation, the program configuration is automatically adopted during setup. Update installations are fully automatic, also with configuration adoption.

There are two installation routines for Log Mail Notification, each requiring administrative rights.

1. Conventional installation via the setup program (GUI)

The setup program guides you graphically through the installation. The program is provided with standard values. On newer Windows versions, changes to Start menu entries (name/icons) may only become visible after logging off/on or restarting.

2. Specific or automatic installation via Console/PowerShell (Silent)

Silent installation (Unattended Setup)

Supported parameters

/VERYSILENT - Completely without user interface (no dialogs)
/SILENT - Minimal interface (progress bar), no interaction
/SUPPRESSMSGBOXES - Suppresses all message boxes (error dialogs, etc.)
/NORESTART - Prevents automatic restart after installation
/RESTART - Forces restart after installation
/DIR="Path" - Set installation directory
/GROUP="Name" - Set Start menu folder
/LOG="Path" - Write installation log

Example: /DIR="C:\Program Files\Log Mail Notification"

Examples for silent installation of Log Mail Notification

LogMailNotification_X-X-X.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /LOG="C:\Temp\LMN_Setup.log"

LogMailNotification_X-X-X.exe /SILENT /DIR="D:\Tools\LogMailNotification" /GROUP="Log Mail Notification"

Note:

For installations with an existing previous installation, the program configuration is automatically adopted during setup. Update installations are fully automatic, also with configuration adoption.

The Windows service is provided under the system context, configured for automatic start, and started. After installation, a sample configuration is available. This includes, among other things, a non-functional sample license. Since the license is not valid, the service will be stopped again. The productive configuration options of Log Mail Notification can be found in the Configuration section.

 

Configuration

To configure Log Mail Notification productively for your needs, the configuration file LogMailNotification.config is available as an XML file in the program directory C:\Program Files\Log Mail Notification. The file Example_LogMailNotification.config is also provided as a configuration template in the program directory.

The configuration file contains the following settings (XML segments). Since version 1.3.x, the log file configuration has been extended so that up to three different log files can be monitored in parallel.

Recommended Procedure for Configuration

1. First, enter Activation (Serial) and Mail Recipients.
2. Then test Log File Monitoring with logfile1/logstring1.
3. Only then add further monitoring with logfile2/logstring2 and logfile3/logstring3.
4. Finally, set the SMTP mode (internal or external), activate test mail, and restart the service.

Note: Changes to the configuration file take effect at the next service start. Then check the entries in the log files and in the event log under Log Mail Notification.

Log File Monitoring

<log>
  <logfile1>C:\Logs\app.log</logfile1>
  <logstring1>Error</logstring1>
  <logfile2>C:\Logs\web.log</logfile2>
  <logstring2>Critical</logstring2>
  <logfile3>C:\Logs\sec.log</logfile3>
  <logstring3>Failed login</logstring3>
  <casesensitiv>false</casesensitiv>
  <loglasttime>60</loglasttime>
</log>

❗ Required

With logfile1 and logstring1 you define the first log file monitoring. Optionally, you can add two more monitorings with logfile2/logstring2 and logfile3/logstring3. This allows you to monitor up to three different log files in parallel.

With casesensitiv you specify whether the search for the keyword is case-sensitive. loglasttime specifies the time window in minutes in which hits are considered.

Empty or incomplete entries are ignored.

Compatibility

The multi-log file monitoring is an extension of the previous configuration. Existing installations with logfile/logstring remain functional. New installations should preferably use the extended structure with logfile1..3 and logstring1..3.

Example for a combined extension in operation: first set only logfile1/logstring1 productively and gradually add further monitorings (2/3) as needed.

Query Interval

<timer>
  <timertime>60</timertime>
</timer>

❗ Required

With timertime under the timer configuration section, you set the query interval for log file monitoring. The value is in minutes, e.g. 60, and accepts values between 5 minutes and 1440 minutes (24 hours).

SMTP Function (Custom Mail Server)

<smtp>
  <smtpserver>smtp.example.com</smtpserver>
  <smtpport>465</smtpport>
  <smtpuser>This email address is being protected from spambots. You need JavaScript enabled to view it.</smtpuser>
  <smtppassword>password</smtppassword>
  <smtppassencryption></smtppassencryption>
  <smtpencryption>SSL</smtpencryption>
</smtp>

✔️ Optional

The values specified under the smtp configuration section are sample data. For use of the internal SMTP function of Log Mail Notification, you can use the sample data as is or leave the individual values empty. This will send emails via the Log Mail Notification mail server. Usage is limited per annual license as follows:

• Log Mail Notification Trial: 30 emails/3 days per license
• Log Mail Notification Standard and Professional: 500 emails/1 year per license
• Log Mail Notification Ultimate: no use of internal SMTP, as the number of computers is not limited.

All versions of Log Mail Notification allow the use of your own SMTP server for email sending. You can refer to the sample data for configuration. Under smtpencryption please select either SSL or TLS. Note: For SSL, port 465 is used by default, and for TLS, port 587 is used. Your mail provider can tell you which configuration is relevant for you.

SMTP Password: Plaintext or Encrypted

• smtppassencryption empty: smtppassword is read as plaintext.
• smtppassencryption set: smtppassword is read as an encrypted value and decrypted at startup.

The tool SmtpPassEnc.exe is provided to generate a compatible encrypted password value. Enter the generated value under smtppassword and set smtppassencryption accordingly.

The same tool can also be used to encrypt the proxy and SOCKS password (see section Proxy Configuration Option, flag passwordencryption).

If decryption fails, Log Mail Notification logs an error in the log file and does not use a valid SMTP password.

Recommended Test Sequence for SMTP

1. Enter external SMTP data completely (server, port, user, password, SSL/TLS).
2. Optionally encrypt the password and set smtppassencryption.
3. Activate sendtestmaillmn=true.
4. Restart the service and check the test mail entry in the log file.

Note: Changes to the configuration file take effect at the next service start. Then check the entries in the Log Mail Notification log file.

SMTP Test for Internal Function

• After installation, a non-functional sample configuration is available.
• Test the internal SMTP functionality with the following configuration (this is how the .config is delivered) or leave the values empty:

<smtp>
    <smtpserver>smtp.example.com</smtpserver>
    <smtpport>123</smtpport>
    <smtpuser>This email address is being protected from spambots. You need JavaScript enabled to view it.</smtpuser>
    <smtppassword>password</smtppassword>
    <smtppassencryption>false</smtppassencryption>
    <smtpencryption>SSL/TLS</smtpencryption>
</smtp>

Mail Recipients for Notifications

<mail>
  <mailtoemail>This email address is being protected from spambots. You need JavaScript enabled to view it.</mailtoemail>
  <mailtoname>Example User</mailtoname>
  <mailccemail></mailccemail>
  <mailccname></mailccname>
</mail>

❗ Required

Under mail you define the main recipient and optionally a CC recipient.

Sending the Test Email

<testmail>
  <sendtestmaillmn>true</sendtestmaillmn>
  <sendtestmailsmtp>true</sendtestmailsmtp>
</testmail>

❗ Required

sendtestmaillmn controls the monthly test mail, sendtestmailsmtp the SMTP start test mail.

General Contact (Organization in the Email)

<contact>
  <contactorganisation>Example Contact Organisation</contactorganisation>
  <contactperson>Example Contact Person</contactperson>
  <contactphone>+12 3456 7890</contactphone>
  <contactmail>This email address is being protected from spambots. You need JavaScript enabled to view it.</contactmail>
</contact>

❗ Required

The information is used as a contact block in emails.

Program Activation / License

<activation>
  <serial>YOUR-SERIAL-HERE</serial>
</activation>

❗ Required

The valid license key must be entered exactly under serial.

Specific Settings

<settings>
  <language>de</language>
  <beta>false</beta>
</settings>

❗ Required

language controls the language output, beta the release of beta updates.

Proxy Configuration Option

<proxy>
  <enabled>false</enabled>
  <useSystem>true</useSystem>
  <url>http://proxy.example.local:8080</url>
  <username></username>
  <password></password>
  <passwordencryption>false</passwordencryption>
  <bypassOnLocal>true</bypassOnLocal>
  <noProxy>*.intranet.local;10.0.0.0/8</noProxy>
  <socks>
    <enabled>false</enabled>
    <type>SOCKS5</type>
    <host>proxy.example.local</host>
    <port>1080</port>
    <username></username>
    <password></password>
    <passwordencryption>false</passwordencryption>
  </socks>
</proxy>

❗ Required

This controls direct connection, system proxy, or explicit proxy/SOCKS usage.

The proxy and SOCKS password can also be stored encrypted. Set passwordencryption to true in the respective section and enter the value generated with SmtpPassEnc.exe under password. With false (or a missing entry) the password is read as plaintext. The flags apply separately to SMTP, proxy and SOCKS.

Usage and Additional Tools

Under Start / Program / Log Mail Notification, you have access to additional features:

• LogTest.exe – Test program for Log Mail Notification

• Links to Log Mail Notification: Release Notes, Website, Support
• Documents: Manual, License
• Tools:
  • Service Configuration (open configuration file)
  • Service Configuration Example (open example configuration file)
  • Service Control (control the Windows service via cmd)

Troubleshooting

For troubleshooting Log Mail Notification, you can use the program's own log files and event log entries. These are visible in the Event Viewer under Application and Service Logs / Log Mail Notification. The logs provide an overview of the following program processes:

• Licensing
• Activation
• Configuration
• Update
• Proxy usage
• Email quota (Trial, Standard and Professional with internal SMTP)
• Log file monitoring (up to 3 configurable log files)
• License expiration notice (info email with daily limit)

When monitoring log files, please pay particular attention to the entries for logfile1/logstring1, optionally logfile2/logstring2 and logfile3/logstring3 in the configuration file.

This information is very helpful and also serves support purposes.

Important event IDs

Event ID	Meaning
1001	Windows service started
1002	Configuration applied
1011	SMTP usage (internal/external)
1012	Internal SMTP counter: x of y
1013	Internal SMTP blocked (quota reached)
1014	Log file monitoring completed successfully
2001	Activation successful
2002	License valid
3001	Warning / retry
3002	Log file issue (not found, access denied)
7001-7004	Error (general, license, activation, CSRF token)

 

Updates

Each time the Windows service Log Mail Notification starts, it checks for updates. If an update is available, it is automatically downloaded and installed in the background. Existing configuration settings are retained and the service is restarted after the update. This process is seamless for the user. If you are interested in the process or the currently installed version, you can view this in the Event Viewer under Application and Service Logs / Log Mail Notification.

The latest information on release notes and changes to Log Mail Notification can be found on our website: https://www.logmailnotification.com/de/software/releasenotes

Support & Contact

Our support is available for the following topics regarding Log Mail Notification via email or ticket system:

• General
• Development
• Licensing
• Feedback

You can reach us at:

Website
www.logmailnotification.com

Support (registration required)
www.logmailnotification.com/de/konto/support

If you would like to leave us feedback or have suggestions for improvement, please let us know via the support page. We would also appreciate your rating or a comment on the purchased version.