summaryrefslogtreecommitdiffstats
path: root/assets/mailsync.sh
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-08-04 12:04:31 +0200
committerDanilo M. <danix@danix.xyz>2026-08-04 12:54:59 +0200
commit74d1da2755ff8e1a47bda676fab7b84e910ef738 (patch)
treee32bcf4a5d752c64255ae779666a504385434813 /assets/mailsync.sh
parent1f25f2b10d995dd0978d5846e175c9094b69f53f (diff)
downloadqtmaildir-74d1da2755ff8e1a47bda676fab7b84e910ef738.tar.gz
qtmaildir-74d1da2755ff8e1a47bda676fab7b84e910ef738.zip
feat(sync): bring mailsync.sh here, print to stdout, exit truthfully
The reference sync script lived in the companion mailctl project, which documents that it never calls it: sync and organization are separate there on purpose. qtmaildir is the only thing that runs it programmatically, and two of its behaviours were live bugs here, so it belongs in this repo where the constraints on it are. It printed nothing a caller could see. Everything was redirected to $LOGFILE, so MailSync captured an empty stream and the sync log pane stayed blank, a known limitation carried since 0.1.0. It now writes to both through tee: cron keeps its log, and the pane has something to show. It also ended in an unconditional exit 0, discarding statuses it had already computed. qtmaildir believes that exit code: a failed mbsync reported success, cleared the unsynced-changes count, and would have allowed a sync-on-exit to quit over a sync that never happened, which is exactly the case the exit prompt exists to prevent. It now exits with mbsync's status, or notmuch's when mbsync succeeded. The statuses move through files rather than shell variables because the run block is piped into tee, which puts it in a subshell where an assignment does not survive. Verified against stub mbsync and notmuch binaries in a fake HOME, so no mail or database was touched: output reaches stdout, the log still gets every line, and a failing mbsync or notmuch produces its own exit code rather than zero. Both properties are now recorded in CLAUDE.md, since they exist for this application's sake and an edit that looks like a cleanup would remove them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'assets/mailsync.sh')
-rwxr-xr-xassets/mailsync.sh102
1 files changed, 102 insertions, 0 deletions
diff --git a/assets/mailsync.sh b/assets/mailsync.sh
new file mode 100755
index 0000000..ee918b6
--- /dev/null
+++ b/assets/mailsync.sh
@@ -0,0 +1,102 @@
+#!/bin/bash
+# mailsync.sh - fetch mail and reindex it.
+#
+# Copyright (C) 2026 Danilo M. <danix@danix.xyz>
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+# Runs mbsync followed by notmuch new, under a lock so a cron timer and a
+# click in qtmaildir cannot run two mbsync processes over one Maildir.
+#
+# Two audiences, which is what shapes the output handling below: a cron or
+# systemd timer, which wants a log file it can read afterwards, and
+# qtmaildir, which runs this as a subprocess and shows what it prints.
+# Output therefore goes to BOTH, and the exit status is real.
+
+# Defensive: don't rely on cron/systemd/whatever invokes this to have
+# set these correctly. Explicit beats inferred, especially after the
+# HOME-not-set failure we hit once already. Fall back to the invoking
+# user's home from passwd rather than a hardcoded path.
+export HOME="${HOME:-$(getent passwd "$(id -u)" | cut -d: -f6)}"
+export GNUPGHOME="${GNUPGHOME:-$HOME/.gnupg}"
+
+LOCKFILE="/tmp/mbsync.lock"
+LOGFILE="$HOME/.local/state/mailsync.log"
+MAX_LOG_BYTES=$((10 * 1024 * 1024)) # rotate past 10MB, see note below
+
+mkdir -p "$(dirname "$LOGFILE")"
+
+exec 200>"$LOCKFILE"
+if ! flock -n 200; then
+ # Both streams again: a caller that skipped because the cron run holds
+ # the lock needs to be told, not left with silence and an error code.
+ msg="$(date -Iseconds) === SKIPPED: previous run still in progress ==="
+ echo "$msg" >> "$LOGFILE"
+ echo "$msg" >&2
+ exit 1
+fi
+
+# Simple rotation: if the log's gotten big, keep the last run's worth
+# and move the rest aside rather than letting it grow forever.
+if [ -f "$LOGFILE" ] && [ "$(stat -c%s "$LOGFILE" 2>/dev/null || echo 0)" -gt "$MAX_LOG_BYTES" ]; then
+ mv "$LOGFILE" "${LOGFILE}.1"
+fi
+
+# Statuses are written to files rather than shell variables because the
+# block below is piped into tee, which puts it in a subshell: a variable
+# assigned in there is gone by the time the parent reads it.
+STATUS_DIR="$(mktemp -d)"
+trap 'rm -rf "$STATUS_DIR"' EXIT
+
+START_TS="$(date -Iseconds)"
+{
+ echo "===== RUN START: $START_TS ====="
+
+ # Timestamp every line of mbsync/notmuch output as it streams,
+ # rather than only marking run boundaries, this is what actually
+ # lets you tell which errors are from which run at a glance.
+ mbsync -a 2>&1 | while IFS= read -r line; do
+ echo "$(date '+%H:%M:%S') $line"
+ done
+ echo "${PIPESTATUS[0]}" > "$STATUS_DIR/mbsync"
+
+ notmuch new 2>&1 | while IFS= read -r line; do
+ echo "$(date '+%H:%M:%S') $line"
+ done
+ echo "${PIPESTATUS[0]}" > "$STATUS_DIR/notmuch"
+
+ END_TS="$(date -Iseconds)"
+ MBSYNC_STATUS="$(cat "$STATUS_DIR/mbsync")"
+ NOTMUCH_STATUS="$(cat "$STATUS_DIR/notmuch")"
+ if [ "$MBSYNC_STATUS" -eq 0 ] && [ "$NOTMUCH_STATUS" -eq 0 ]; then
+ echo "===== RUN END: $END_TS status=OK ====="
+ else
+ echo "===== RUN END: $END_TS status=FAILED mbsync=$MBSYNC_STATUS notmuch=$NOTMUCH_STATUS ====="
+ fi
+# tee, not a plain redirect. Appending only to the log left every caller
+# that runs this as a subprocess with nothing to show: qtmaildir's sync
+# pane was empty for exactly this reason. Cron still gets its log.
+} 2>&1 | tee -a "$LOGFILE"
+
+MBSYNC_STATUS="$(cat "$STATUS_DIR/mbsync" 2>/dev/null || echo 1)"
+NOTMUCH_STATUS="$(cat "$STATUS_DIR/notmuch" 2>/dev/null || echo 1)"
+
+# Report the real outcome. The old unconditional "exit 0" meant a caller
+# could not distinguish a clean sync from a failed one, so qtmaildir's
+# sync-on-exit prompt would report success over a sync that had not
+# happened, which is precisely the case that loses work.
+if [ "$MBSYNC_STATUS" -ne 0 ]; then
+ exit "$MBSYNC_STATUS"
+fi
+exit "$NOTMUCH_STATUS"