Skip to content

Archiving to Hyperkitty fails because of invalid Message-ID.

We occasionally see attempts to archive messages failing because of invalid Message-ID: headers. Partial headers of an example are

Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====@microsoft.com]>
From: NuGet Gallery <support@nuget.org>
To: pythonnet-dev@python.org
Date: Thu, 02 Feb 2023 23:03:02 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=-XLkOGJV26YWwUy93O2lysQ=="
X-MS-TrafficTypeDiagnostic: 
	CO1NAM11FT061:EE_FirstParty-ICP-V3-System|SA0PR19MB4351:EE_FirstParty-ICP-V3-System
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 815d62b7-86b4-4d73-514c-08db05b4b14b
X-MS-Exchange-SenderADCheck: 0
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 
	1Po1jTFiPLnSt9Tf4xWrb4h5uTq6pD8mjC7ZOHXPzlvJpekWnkNUWlfAeeBK/MmmbsO3Nblk4OOILDUdqBafcusROMRtb2bIgR6NH9Ly9zA9+wrsxRXk/fNHGCo7Q/DplmP1WVRb+AcBDr2lyp7xHZFzlfze0lDUKGSfU2nLWcwfy92r0Cjvwr/8Z0DrmTXW1qcw7jOhzVhP3Bcui+rA1WGcnpeI42VZdqGkt9ArybyoiqnoRovhamV4oEN4xk/rKMr40cIKXV2eg5SuiyEEERh8YcDVwtgDjydRozqZTYgRhSo2lDNztb9I6/nrMvu79QCUxftIUYilfa3Xn9IsKXbUDMBKQDq0pQN5r5EMy2ayKovIcwa9kawAK4+z/JCA3Q8MP5myI8v77oNVKk/9NAEh6krWFH9KwlSwF6Z35hckxP72SUXa3yQAVLZE5fc7qZfDCBYq3Jv7XztBHYJ4Rf/CjjSpVP5cakOshDV0gMBt3m2i+vDGJJ9dyTxmNO6nMboErAbK6KaqXO0dMAyKWjEAdVb5ug/gGWHdz0lJ1l1MyJDwdkU4B5JJXno7zCK5K1l+ErFlBlLOMKZlFoocbfuHbjmeLnnhOLhkhciS060zvmAs2olIga+llh77qtAq0eScLeOJZshCeDaBbGEjERTQUqEVCfKkC7+x8vowuK+J2TxhhGHbzjTrQTO1ioHxb4FmLS6LBuDkwWA9lME8S5oXl5F7Q13U/M0k6QnMdz62jvtr//X03y8M+kkCXLTFM2xmTEE7rgdFmyyaBIccNdrfrsSUZbu2OaT3lEVEYZlF+CIa5znUWb5RMFWOpkcWqN2buu1/xVieN7xVHsyTtQ==
X-Forefront-Antispam-Report: 
	CIP:51.141.168.191;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MW1PEPF00002D81;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(13230025)(6029001)(376002)(136003)(396003)(34036004)(346002)(39830400003)(448600002)(451199018)(6496006)(6486002)(38610400001)(83380400001)(586005)(52230400001)(336012)(81166007)(356005)(9316004)(166002)(41320700001)(86362001)(76236004)(9686003)(121820200001)(956004)(61793004)(26005)(33964004)(8936002)(36736006)(5660300002)(41300700001)(8676002)(68406010)(66899018)(2906002)(45080400002)(31460500070)(30990500010)(15585785002);DIR:OUT;SFP:1020;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: 
	QTWIQLkrKlOEb/lHzEPQVz5DTOFBlsVTUqd0s5tirFdlh/zWRdpkChAITp+0Jf65dMbKXO76ICJeAkmkEJtmd9xmVBbnA5NjObt6PtVenrGMFsH1gCCODoB8/5oGaugPmx/OdgvfE31JMTWcKFIfNlggr8vFDTyrcaeY74+BREH+vdLJElv0i8wztqovQVD6tx6Nqbo5PI/p1oICRGd50HVT0BjlYVbZPHQoF6syMrNHZS1jOhGaeQgadm34FeBmAEHpJycHWK6cnNYD7Oq32QLkkFc52J3nFz46VcifSAu6SqnZY8YACjgHD1l+e57/2XJr4oqCCatmI9D+wwd21bGYsozcY/NCt5PuO8t0W+s82R8cTjjEM/Bjyw5faYNSlqoH81W1nRJ7+bwaHsD0WST2s+Nen3WONTys+7rrxyFcky8NT3l93HOc+7gXoxqN995JJPeexGBZzwFMdZ3HUR0yWDazrVVigNTgseF3XMw=
X-OriginatorOrg: ideasprod01.microsoft.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2023 07:03:02.9656
 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 815d62b7-86b4-4d73-514c-08db05b4b14b
X-MS-Exchange-CrossTenant-Id: 18c419b0-1db9-44f4-be63-47079b773f99
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=18c419b0-1db9-44f4-be63-47079b773f99;Ip=[51.141.168.191];Helo=[MW1PEPF00002D81]
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: TreatMessagesAsInternal-CO1NAM11FT061.eop-nam11.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA0PR19MB4351

I've seen this more than once. I don't know for sure what MUA is creating these defective Message-ID: headers, but we need to defend against it because otherwise they get queued and continuously retried by mailman_hyperkitty.