TautWeekly for Plex v0.26.0

Released: 2026-09-09

Personalized delivery for managed Plex users

An active Tautulli user without a native email can now receive a personalized
newsletter through a private administrator-assigned fallback address. After
Tautulli discovery, Manager Config shows a separate Managed-user delivery
addresses card only when such a user exists. The existing delivery-exclusions
card and its behavior remain unchanged. Each fallback is keyed by the stable
numeric Tautulli user ID, shared inboxes are allowed, and an assignment for a
temporarily undiscovered or deleted ID remains preserved until an administrator
explicitly removes it.

Clearing an address removes only that assignment. It does not alter newsletter
history or welcome state, and the user returns to the normal missingEmail
skip result. A failed live discovery refresh leaves both the last valid
sanitized choices and the private saved assignments intact.

Fixed recipient precedence

Every production path now applies the same order:

1. skip inactive or deleted users;
2. apply ExcludedUserIds;
3. use the native Tautulli email when present, otherwise the configured
   fallback;
4. skip a missing effective address; and
5. apply ExcludedEmails to the effective address.

A fallback can never replace or redirect a native Tautulli email. Confirmed
SendAll, confirmed one-off welcome, scheduled delivery, and deleted-item
cache coverage use the effective recipient. Preview generation and all
TestEmail modes retain their existing sample-user and controlled-recipient
isolation.

Changing the map is a recipient-coverage change. A Manager save regenerates
previews and refreshes enabled cache coverage through the existing no-email
post-save operation.

Privacy boundary

UserEmailOverrides is private configuration. It can appear in config.json
and private configuration backups, so both require the same filesystem and
sharing protections as SMTP credentials. Authenticated Config editing can read
and change the map.

Sanitized discovery and its retained cache expose only stable ID, display name,
role, eligibility, and an address-needed Boolean. Redacted configuration
summaries, operation history/results, diagnostics, and shareable cache reports
contain neither the map nor any fallback address. Public GUI-preview data is
fictional and follows the same redaction contract.

Validation boundary

Automated coverage exercises Manager validation and atomic backup behavior,
orphan preservation, duplicate shared inboxes, discovery-failure retention,
accessible desktop/mobile controls, privacy serialization, production
precedence, SendAll, one-off welcome, TestEmail isolation, cache warming,
PowerShell 5.1/7 portability, all maintained source copies, and all five release
archives. Live SMTP/provider acceptance remains the operator's controlled
TestEmail responsibility before scheduled delivery is enabled.

See Configuration,
Security, and the applicable platform
Quickstart for setup and recovery guidance.