Truemailer Desktop 0.1.13

Truemailer Desktop 0.1.13

Highlights

• Two-queue sending - Queue A and Queue B share sending lanes; outcomes sync in the background for smoother throughput.
• Recovery - Restores saved results after restart; uncertain SMTP attempts stay under review in the campaign dashboard.

Requires

• Truemailer Cloud with migration 0064 and the v2 Desktop API deployed (./deploy.sh on the main monorepo) before installing or updating to 0.1.13.

Upgrade

Download from truemailer.in/download or in-app Check for updates.

Windows: Truemailer-Desktop-Setup-0.1.13.exe - GitHub Releases v0.1.13

Truemailer Desktop 0.1.11

Truemailer Desktop 0.1.11

Highlights

• Direct Cloud API - packaged Desktop uses https://api.truemailer.in for all device API calls (work, heartbeat, token refresh, pairing). Fewer Connection interrupted / UPSTREAM_UNAVAILABLE blips when only the web dashboard (truemailer-web) reloads during deploy.
• Connect device unchanged - Connect device still opens https://www.truemailer.in in your browser to sign in and approve; Cloud returns that link, not the API host.

Upgrade

Download from truemailer.in/download or in-app Check for updates.

Windows: Truemailer-Desktop-Setup-0.1.11.exe - GitHub Releases v0.1.11

Requires

• api.truemailer.in nginx → Fastify healthy (same as today).
• VPS APP_URL remains https://www.truemailer.in so pairing URLs stay correct.

Truemailer Desktop 0.1.10

Truemailer Desktop 0.1.10

Highlights

• Revoked vs Connection interrupted — confirmed revoke shows Revoked instead of endless Connecting after a dead refresh token
• Activity visibility — prefetch / next-batch Cloud errors (including codes like UPSTREAM_UNAVAILABLE) appear in Activity, not only the log file
• Safer refresh on network blips — transient fetch failures during token refresh no longer throw and abort recovery
• Settings — packaged builds show Cloud API URL (https://www.truemailer.in/api) and Device ID for campaign assignment checks

Requires

Deploy Truemailer Cloud with the matching API/web changes (resume-sending queue heal, ghost batch reconcile, token refresh 400 validation) before relying on Resume sending for stuck desktop campaigns.

Stuck campaign after re-pair

1. Desktop Ready (green) — re-pair if still Connecting
2. Dashboard → campaign → Resume sending (green confirmation banner)
3. Match Device ID in Settings to Cloud Desktop clients / manual assignment list

Upgrade

Download from truemailer.in/download or in-app Check for updates.

Windows 10 or later: Truemailer-Desktop-Setup-0.1.10.exe — GitHub Releases v0.1.10

Truemailer Desktop 0.1.9

Truemailer Desktop 0.1.9

Highlights

• Fixes false Not paired when multiple parts of the app refresh the session at the same time (prefetch, heartbeat, batch work)
• Single-flight refresh everywhere — startup recovery uses the same path as API retries
• Real token expiry from Cloud (persisted expiresAt) instead of assuming one hour from each app start

Requires

Deploy Truemailer Cloud with idempotent desktop token refresh (30s cache on duplicate refresh during rotation) before installing or updating to 0.1.9.

Support macro

If a user is already Not paired after the old bug cleared local secrets: upgrade to 0.1.9, then Connect device once if Cloud → Desktop clients still shows the device as active (not revoked).

Upgrade

Download from truemailer.in/download or in-app Check for updates.

Windows 10 or later: Truemailer-Desktop-Setup-0.1.9.exe - GitHub Releases v0.1.9

Truemailer Desktop 0.1.8

Truemailer Desktop 0.1.8

Highlights

• Fixes false Revoked status when Truemailer Cloud has a brief deploy or outage while Desktop is sending
• Connection interrupted / Reconnecting with automatic session retry and Retry now on Status
• Connect device only when Cloud confirms the device was revoked

Support macro (for teams on 0.1.7 and earlier)

If a user reports Revoked after a deploy: ask them to fully quit and reopen Desktop. Connect device is only needed if Cloud → Desktop clients shows the device as revoked.

Upgrade

Download from truemailer.in/download or in-app update when published.

Truemailer Desktop 0.1.7

Truemailer Desktop 0.1.7

Changed

• Faster handoffs between batches - bulk send-attempt marking, overlapped next-batch prefetch with result sync, skip redundant ack when Cloud returns batchClaimed
• Performance logging - BATCH_PERF and PREFETCH_PERF in the desktop log file (Settings → Open logs folder)

Requires

• Truemailer Cloud with matching desktop work API (attempt-bulk, auto-claim on assign). Cloud must be deployed before upgrading from 0.1.6.

Verify

Compare Activity and log Batch handoff total= after 2–3 batches. See repo docs: docs/batch-gap-performance-baseline.md.

Truemailer Desktop 0.1.6

Truemailer Desktop 0.1.6

Changed

• Concurrent sends per mailbox (1–16, default 4) and total concurrent sends (1–64, default 16 for new installs) in Settings
• Fair round-robin scheduling across mailboxes in each batch so one account does not starve the rest

Notes

• Higher concurrency can increase throughput but may trigger provider throttling, temporary SMTP errors, or authentication limits.
• No Truemailer Cloud deploy required — settings are local to each Desktop app.
• Upgrades keep your saved total concurrent value; per-mailbox concurrency defaults to 4 the first time you open Settings after update.

Field verification (recommended after changing limits)

On a real mailbox (e.g. Microsoft 365), compare Activity sends/hour and SMTP errors at 1, 4, 8, and 16 concurrent sends per mailbox before maxing limits in production.

Windows 10 or later: Truemailer-Desktop-Setup-0.1.6.exe

Truemailer Desktop 0.1.5

Truemailer Desktop 0.1.5

Fixed

• Active batch assigned idle stall - automatically releases or resumes Cloud orphan batches within seconds (no ~10 minute lease wait).
• Orphan assignments after app restart (including from 0.1.4 prefetch) are cleared or resumed on startup.

Changed

• Status and Activity show Recovering batch assignment when Cloud cleanup takes longer than expected.

Requires Truemailer Cloud deploy with POST /v1/desktop/work/reconcile-active (same VPS deploy as API + scheduler).

Windows 10 or later: Truemailer-Desktop-Setup-0.1.5.exe

Truemailer Desktop 0.1.4

Truemailer Desktop 0.1.4

Continuous batch pipeline

• After the last send results are confirmed on Cloud, the next batch is requested in the background while the app cleans up locally.
• Next batch ready appears in Activity when acquisition finishes (with timing for support).
• Shorter gaps between batches on long campaigns; SMTP per-message speed is unchanged.

Fixes

• Pause / quit releases prefetched batches on Cloud.
• Windows notifications use Truemailer Desktop branding (not electron.app.…).

Windows 10 or later: Truemailer-Desktop-Setup-0.1.4.exe

Truemailer Desktop 0.1.3

Truemailer Desktop 0.1.3

Batch interrupted fix

• Failed completeBatch calls no longer orphan work on Truemailer Cloud while the app shows Ready.
• Unsynced send results are saved locally and retried automatically when Cloud is reachable again.
• Persistent sync failures release the batch back to Cloud for reassignment.
• Heartbeats stay busy during result sync so campaigns keep making progress.

Support

• Settings → Open logs folder opens %APPDATA%\@truemailer\desktop\logs\truemailer-desktop.log.

Cloud (deploy API + scheduler)

• Scheduler ghost batch heal recovers in-progress batches when a device is online but idle (~2 min tick).

Windows 10 or later: Truemailer-Desktop-Setup-0.1.3.exe