summaryrefslogtreecommitdiffstats
path: root/assets
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-08-07 11:08:54 +0200
committerDanilo M. <danix@danix.xyz>2026-08-07 11:08:54 +0200
commit1a6007b4cdaacb22d013daeb58deb6ae72afda07 (patch)
treec986469082a6dde16a227ba3bde25f5ccd694582 /assets
parent28e6ea321d742d26fa07d3ae6f403e6bd9baacbe (diff)
downloadqtmaildir-1a6007b4cdaacb22d013daeb58deb6ae72afda07.tar.gz
qtmaildir-1a6007b4cdaacb22d013daeb58deb6ae72afda07.zip
docs: record how to find the messages item 41 affected
Confirmed on real mail: a message whose text/html part carries a Content-Id now renders. Item 41's status drops the caveat about the reported message not being relocated. Finding an affected message is harder than it looks, which is why the search is worth recording rather than rederiving. A Content-Id on an inline image is the common case and always worked, so a plain grep for the header returns mostly noise. The narrow case is a Content-Id in the same header block as a text/html Content-Type, which needs a small awk pass over the message files. That found 96 in one inbox, all bulk senders. Also records that file: is not a notmuch search term, so a matched path cannot be turned into a query directly; the Message-ID header is the way across to an id: query. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'assets')
0 files changed, 0 insertions, 0 deletions