apple-mail-mcp 2.19.0 → 2.19.2

package/README.md

@@ -331,6 +331,16 @@ List messages in a mailbox.
 
 **Returns:** List of messages with ID, date, subject, and sender.
 
+⚠️ **Row dates differ by backend.** On the **IMAP** path each row carries both
+`dateSent` (the message's `Date:` header) and `dateReceived` (mailbox arrival —
+`INTERNALDATE`, falling back to the header date if the server withholds it).
+They differ legitimately by transit time; when they differ by **years**, the
+mailbox was migrated or re-imported and the arrival timestamp was reset — trust
+`dateSent` for chronology ([#224](https://github.com/sweetrb/apple-mail-mcp/issues/224)).
+On the **AppleScript** path rows carry only `dateReceived` (Mail's `date
+received`); `dateSent` is not yet emitted there. Sort order keys on the header
+date on both backends, which is the stable one.
+
 ---
 
 #### `send-email`

package/build/cli.js

@@ -58093,13 +58093,25 @@ function formatRow(m, account, path) {
   const read = m.flags?.has("\\Seen") ? "read" : "unread";
   return `  - ID: ${encodeImapId(account, path, m.uid)} | ${date} | ${subject} (from: ${from}) [${read}]`;
 }
+function isoOrEmpty(d) {
+  if (!d) return "";
+  const parsed = d instanceof Date ? d : new Date(d);
+  return Number.isNaN(parsed.getTime()) ? "" : parsed.toISOString();
+}
 function structuredRow(m, account, path) {
   const env = m.envelope ?? {};
   return {
     id: encodeImapId(account, path, m.uid),
     subject: env.subject || "(no subject)",
     sender: senderName(env.from),
-    dateReceived: env.date ? new Date(env.date).toISOString() : "",
+    // ⚠️ `env.date` is the `Date:` HEADER — imapflow builds ENVELOPE from the
+    // header block — so emitting it as `dateReceived` made the same field name
+    // mean "sent" here and "arrived" on the AppleScript path. Both are now
+    // emitted under the name that is true of them, matching `messageSummary`.
+    // `dateReceived` falls back to the header date when the server withheld
+    // INTERNALDATE, which is the old behaviour and never invents a value.
+    dateSent: isoOrEmpty(env.date),
+    dateReceived: isoOrEmpty(m.internalDate ?? env.date),
     isRead: m.flags?.has("\\Seen") ?? false,
     isFlagged: m.flags?.has("\\Flagged") ?? false,
     flagColorIndex: mailFlagColorIndex(m.flags),
@@ -58145,7 +58157,11 @@ async function fetchMailboxMatches(client, path, criteria, newestCount) {
       // BODYSTRUCTURE rides along so `hasAttachments` is computed rather
       // than assumed. Measured on 50 real messages: ~390ms -> ~465ms for
       // the fetch (~17%), same single round trip, no extra request.
-      { envelope: true, flags: true, bodyStructure: true },
+      //
+      // INTERNALDATE rides along for the same reason, and is why `dateReceived`
+      // can finally mean what it says: imapflow's `envelope.date` is built from
+      // the header block, so it IS the `Date:` header, not arrival time.
+      { envelope: true, flags: true, bodyStructure: true, internalDate: true },
       { uid: true }
     )) {
       byUid.set(msg.uid, msg);

package/build/index.js

@@ -65132,7 +65132,7 @@ function splitIds(raw) {
   return raw.split(/[\s,]+/).map(bareId).filter(Boolean);
 }
 function parseHeaderBlock(input) {
-  const text = (input ?? "").replace(/\r\n/g, "\n");
+  const text = (input ?? "").replace(/\r\n|\r/g, "\n");
   const blank = text.search(/\n\n/);
   const raw = (blank === -1 ? text : text.slice(0, blank)).replace(/\n+$/, "");
   const headers = [];
@@ -65503,13 +65503,25 @@ function formatRow(m, account, path) {
   const read = m.flags?.has("\\Seen") ? "read" : "unread";
   return `  - ID: ${encodeImapId(account, path, m.uid)} | ${date3} | ${subject} (from: ${from}) [${read}]`;
 }
+function isoOrEmpty(d) {
+  if (!d) return "";
+  const parsed = d instanceof Date ? d : new Date(d);
+  return Number.isNaN(parsed.getTime()) ? "" : parsed.toISOString();
+}
 function structuredRow(m, account, path) {
   const env = m.envelope ?? {};
   return {
     id: encodeImapId(account, path, m.uid),
     subject: env.subject || "(no subject)",
     sender: senderName(env.from),
-    dateReceived: env.date ? new Date(env.date).toISOString() : "",
+    // ⚠️ `env.date` is the `Date:` HEADER — imapflow builds ENVELOPE from the
+    // header block — so emitting it as `dateReceived` made the same field name
+    // mean "sent" here and "arrived" on the AppleScript path. Both are now
+    // emitted under the name that is true of them, matching `messageSummary`.
+    // `dateReceived` falls back to the header date when the server withheld
+    // INTERNALDATE, which is the old behaviour and never invents a value.
+    dateSent: isoOrEmpty(env.date),
+    dateReceived: isoOrEmpty(m.internalDate ?? env.date),
     isRead: m.flags?.has("\\Seen") ?? false,
     isFlagged: m.flags?.has("\\Flagged") ?? false,
     flagColorIndex: mailFlagColorIndex(m.flags),
@@ -65555,7 +65567,11 @@ async function fetchMailboxMatches(client, path, criteria, newestCount) {
       // BODYSTRUCTURE rides along so `hasAttachments` is computed rather
       // than assumed. Measured on 50 real messages: ~390ms -> ~465ms for
       // the fetch (~17%), same single round trip, no extra request.
-      { envelope: true, flags: true, bodyStructure: true },
+      //
+      // INTERNALDATE rides along for the same reason, and is why `dateReceived`
+      // can finally mean what it says: imapflow's `envelope.date` is built from
+      // the header block, so it IS the `Date:` header, not arrival time.
+      { envelope: true, flags: true, bodyStructure: true, internalDate: true },
       { uid: true }
     )) {
       byUid.set(msg.uid, msg);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "apple-mail-mcp",
-  "version": "2.19.0",
+  "version": "2.19.2",
   "description": "MCP server for Apple Mail - read, search, send, and manage emails via Claude and other AI assistants",
   "type": "module",
   "main": "build/index.js",