From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 42DC71F4C0;
	Fri, 25 Oct 2019 02:28:00 +0000 (UTC)
Date: Fri, 25 Oct 2019 02:28:00 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Subject: what should happen when mda sees multiple List-ID headers?
Message-ID: <20191025022800.GA29369@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

Given my recent traumatic experience[*] around multiple
From/To/Cc/Subject headers; I guess we should prepare for the
possibility of multiple List-ID headers showing up in -mda.

Right now, we handle the first one (and I'm updating -learn to
support List-ID, too); but it's possible that multiple List-ID
header can map to different inboxes, too...

[*] https://public-inbox.org/meta/20191016211415.GA6084@dcvr/