{"thread":{"id":"63298","subject":"RFC2822 Message-ID corrupted on some email servers when using git send-email","startedAt":"2025-04-15T14:40:03Z","lastAt":"2025-04-15T14:40:03Z","messageCount":1,"participants":["windowsair"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"516199","messageId":"8771714B848C3A9F+9f64a309-ff70-466f-8d29-15950318b728@airkyi.com","threadId":"63298","inReplyTo":null,"subject":"RFC2822 Message-ID corrupted on some email servers when using git send-email","fromName":"windowsair","fromEmail":"dev@airkyi.com","sentAt":"2025-04-15T14:39:49Z","receivedAt":"2025-04-15T14:40:03Z","isPatch":false,"sender":{"key":"dev@airkyi.com","avatar":null},"body":"Hi there!\n\nI am using `git send-email` to send emails and noticed a behavioral difference between different versions of Git. Since version v2.41.0, the Message-ID has been corrupted on my email provider exmail.qq.com.\n\nThe broken Message-ID may be like this:\n\n         Message-ID: <C627A112429DDE18+20250415123427.20834-3-dev@airkyi.com>\n\nAnd in the early version, the normal Message-ID looks like this:\n\n         Message-ID: <20250415123238.17341-3-dev@airkyi.com>\n\nIt appears that the email server is overriding this field. And I finally found this commit:\n\n         647a2bb3ffc0(\"Merge branch 'jc/spell-id-in-both-caps-in-message-id'\")\n\nThis commit consistently spell \"Message-ID\" as such, not \"Message-Id\".\n\nIt seems that for my email server, using \"Message-Id\" results in the expected unmodified ID, while using the RFC2822-compliant \"Message-ID\" does not. So I want to document this here in case others encounter the same issue in the future :)\n\n\n\nBest regards,\nwindowsair\n\n"}]}