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

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).