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

Information - 31.05.2026

This update enhances the security of the network configuration, renews the quick guides, and updates important components for improved stability and security.

New features

• Encrypted passwords for proxy: Credentials for proxy and SOCKS connections can now be stored encrypted – no longer only for email delivery. Encryption can be enabled separately for each area.
• Revised quick guides: The quick guides (German and English) have been recreated, given a clearer layout, and extended with the password encryption. They are shipped as PDF with the installation.

Improvements

• More security: Sensitive passwords no longer need to be stored in plain text in the configuration.
• Updated components: Important libraries have been brought up to date – among others for email delivery and encryption.
• Extended documentation: Manual and quick guides describe the new encryption options step by step.

Technical changes

• Configuration extended: The passwordencryption element is now also available in the proxy and socks sections and can be set there separately to true or false.
• Dependencies updated: Security and stability updates of the components in use.

Important notes

• Existing configuration remains valid: Existing configuration files continue to work unchanged. If passwordencryption is not set, the password is used as plain text as before – an adjustment is only required if you want to enable encryption.
• Restart the service: After the update, restart the Log Mail Notification service once.
• Encrypt passwords: The bundled SMTP Password Encryption tool is available to generate encrypted values (see manual and quick guide).

Information - 28.04.2026

This release improves license activation, extends setup installers with postinstall options, and updates important dependencies for enhanced stability and security.

New features

• Setup installer extended: New checkboxes on the finish page allow direct opening of the configuration file in Notepad and the online manual in the browser.
• Enhanced diagnostics: Improved diagnostic output in Event Viewer for better error analysis.

Improvements

• License activation optimized: Improved activation process for more reliable license validation.
• Network communication improved: Optimized HTTP architecture for more stable connections.
• Email libraries updated: Latest versions for improved TLS/SSL handling and email processing.
• Code quality improved: Consistent error handling and structured exception handling.

Technical changes

• HTTP communication modernized: Enhanced processing of network requests.
• Architecture revised: Optimized implementation for more stable connections.
• Proxy support extended: Improved compatibility with various network configurations.

Important notes

• Restart the service: After the update, restart the Log Mail Notification service once.
• Use setup options: The new finish page checkboxes simplify initial configuration after installation.

Information - 12.04.2026

With version Log Mail Notification 1.3.2, you benefit from an even more reliable and stable application. The update logic and email security have been further improved. All known issues from the previous version have been resolved.

New Features

• Enhanced security: SMTP password encryption has been optimized.
• Simplified update management: Update management is now easier and more transparent.

Improvements

• More stable operation: All known issues from the last version have been fixed.
• Optimized configuration: Email delivery and license check settings have been further improved.
• More transparency in emails: Notifications now include additional system information such as computer name and FQDN/domain.
• Robust license and startup logic: Improved retry and error handling for license issues.

Technical Changes

• License check with retry logic: Repeated license checks in the background with clean cancellation path.
• License expiration email limited: Sent at most once per day and only if the service previously ran with a valid license.
• Time window-based log detection: Notification path without hard filtering, ensuring consistent configuration logic.

Important Notes

• Restart the service: After the update, the Log Mail Notification service should be restarted once.
• Check configuration: For multiple monitoring, please ensure the new entries logfile1..3 and logstring1..3 are fully set (file + search term per slot).
• Test email recommended: After the update, perform a quick test of the notification delivery.
• License expiration path: The expiration email path is implemented and should be observed during the first real expiration event in operation (event log / service log).

Information - 10.04.2026

This release significantly improves day-to-day use of Log Mail Notification: multiple log monitors, clearer notifications, and more robust behavior during license server issues. Existing configurations remain compatible to ensure a smooth upgrade.

New features

• Up to 3 log monitors in parallel: In addition to logfile/logstring, you can now use logfile1..3 and logstring1..3 in parallel.
• Customer-friendly license expiry email: When a license expires, a clear notification email is sent with renewal information.

Improvements

• Backward compatibility preserved: Existing configurations using logfile/logstring continue to work unchanged.
• More transparency in notifications: Relevant emails now include additional system information such as computer name and FQDN/domain.
• More resilient license handling: Instead of stopping immediately, the service now follows a hardened retry window with clearer failure paths.
• Expected time-window behavior: Matches inside the configured time window can be reported again on later runs (no one-time over-deduplication).

Technical changes

• License retry hardening: Background license retry every 1 hour within a 24-hour window; wait path is cleanly cancelable via CancellationToken.
• License-expiry mail limiting: Sent at most once per day, and only if the service has previously run successfully on that system.
• Time-window based log detection: Active delivery path does not use hard Record/Cursor filtering, so behavior stays consistent with timertime and loglasttime.

Important notes

• Restart the service: After the update, restart the Log Mail Notification service once.
• Check configuration: For multi-monitoring, configure each slot completely (logfile1..3 together with logstring1..3).
• Recommended delivery test: Send a quick test notification after updating.
• License-expiry path: The expiry-mail path is implemented and should be observed during the first real expiry event (Event Log / service log).

Information - 06.03.2026

This version strengthens the stability and security of mail delivery and improves the internal handling of email addresses in Log Mail Notification.

New features

• This release does not introduce any new visible end-user features. The focus is on internal improvements in the mail subsystem.

Improvements

• More robust sender/recipient handling: Processing of special input in email addresses has been improved to avoid unwanted effects when sending via SMTP.
• More stable mail delivery: Internal adjustments in the mail subsystem increase reliability when delivering notifications, especially in environments with strict SMTP rules.
• General application security: Internal mail and log processing has been consolidated with a focus on error tolerance and security.

Technical changes

• Reworked mail components: The components responsible for constructing and sending emails have been updated and aligned with current security requirements in SMTP environments.
• Improved input validation: The internal handling of string values used for sender and recipient information has been hardened to catch problematic input early.

Important notes

• Restart the service: After the update, the Log Mail Notification service should be restarted once so that all changes in the mail subsystem take effect.
• Recommended function test: After the update, you should send a test notification email to verify the correct configuration of the mail server and sender addresses.

Information - 05/03/2026

This version improves the reliability of log file monitoring in proxy/Squid environments, increases privacy in Event Logs and adds a convenient service control script for Log Mail Notification.

New Features

• Squid/Apache log support: Log Mail Notification now detects timestamps in Squid/Apache style ([05/Mar/2026:13:15:46 +0100]) and uses them for time-window evaluation.
• Multiple brackets in log lines: In proxy logs with several bracket pairs (e.g. (squid-1)[59757]...[05/Mar/2026:13:15:46 +0100]) all [...] blocks are inspected until a valid timestamp is found.
• ServiceControl_LMN.bat: New service control script for the Log Mail Notification Windows service with menu (start/stop/restart/status), UAC elevation, PowerShell status lookup and single-key selection.

Improvements

• Correct time-window checks for proxy logs: Alert e‑mails for old entries (e.g. Squid logs) are no longer repeated once they are outside the configured loglasttime window, even if the log file continues to grow.
• Preference of line timestamps: If a valid timestamp is detected inside the log line, it is used for evaluation; the File.GetLastWriteTime() fallback is only used for log formats without any time information.
• Privacy-friendly proxy diagnostics: Proxy diagnostic messages in the Event Log now show abstracted targets (Activation, Webservice, Update or hostname) instead of full URLs.
• Consistent service control UX: The console output of ServiceControl_LMN.bat has been aligned with the known EMN script (clean menu, no visible batch commands).

Technical Changes

• Extended timestamp parser: The function that extracts timestamps from log lines now also supports dd/MMM/yyyy:HH:mm:ss inside [...] and iterates over all bracket pairs in the line.
• Anonymised proxy logging: In Log Mail Notification, proxy diagnostics are now logged as Net: proxyMode=...; proxy=...; effective=Activation/Webservice/Update.
• Robust console output: The service control script explicitly sets @echo off inside the menu to avoid display issues caused by encoding/BOM or code page differences.

Important Notes

• Configuration: For log files in Squid/proxy format, logfile, logstring, casesensitiv and loglasttime should be configured as recommended in the manual (e.g. timertime=5 and loglasttime=15).
• Upgrade from 1.1.4/1.1.5: After updating, the Windows service should be restarted once so that the extended timestamp detection and proxy logic become active.
• ServiceControl_LMN.bat: The script requires administrative privileges; UAC elevation is triggered automatically when the script is started.

Information - 23.02.2026

This version brings modern Position Tracking, automatic log rotation detection, and improved transparency through new Event-IDs.

New Features

• Position Tracking: The system remembers the last read position in the log file. With each scan, only new lines are read – this prevents duplicate alarms and improves performance by a factor of 60.
• Automatic Log Rotation Detection: When log files are recreated daily or hourly, the system automatically detects this and resets the position (Event-ID 1015).
• File.GetLastWriteTime() Fallback: For log files without timestamps in their lines, the file modification time is used for time window verification.
• Log File Monitoring: New configuration parameters logfile, logstring, and casesensitiv replace the previous Windows Event parameters.

Improvements

• New Event-IDs for better transparency:
  • 1014: Log scan completed successfully (match found)
  • 1015: Log rotation detected, position reset
  • 3002: Log file problem (not found, access error)
• Bilingual Event Log messages: All Windows Events appear in German or English based on the configuration (language).
• Extended documentation: New documents for Position Tracking, Event-IDs, and PowerShell script Get-LMNEvents.ps1 for exporting Event Logs to JSON/CSV.
• State Management: Position files are stored under C:\ProgramData\LMN\state\ and survive service restarts.

Technical Changes

• Configuration parameters logevent and logid have been replaced by logfile, logstring, and casesensitiv.
• Event Log entries now show the detection method (line timestamp vs. file modification time).
• Position Tracking uses hash-based state files for unique association with log files.

Documentation

• Manual completely updated with log file monitoring and workflow explanation.
• New documentation: WINDOWS-EVENTLOG-REFERENCE.md, POSITION-TRACKING-GUIDE.md, POSITION-TRACKING-SCHNELLSTART.md.
• PowerShell script Get-LMNEvents.ps1 updated with new Event-IDs.

Important Notes

• Recommendation: The value loglasttime should be 3-4× larger than timertime, e.g., timertime=5 and loglasttime=15.
• When updating from version 1.1.x: Check configuration template under C:\Program Files\Log Mail Notification\Example_LogMailNotification.config.

Information – 01.02.2026

Finalized production deployment with security audit.

Improvements

• Email quota for using the internal email dispatch
• Fail-fast principle to improve application stability
• Fixed resource leaks and implemented config robustness

Fixed

• Updated protocol logs
• Extended web service