From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin@linuxfoundation.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS3215 2.6.0.0/16
X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.2
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 15D971F9F4
	for <meta@public-inbox.org>; Fri, 19 Nov 2021 20:49:19 +0000 (UTC)
Received: by mail-il1-x129.google.com with SMTP id e8so11446469ilu.9
        for <meta@public-inbox.org>; Fri, 19 Nov 2021 12:49:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=linuxfoundation.org; s=google;
        h=date:from:to:subject:message-id:mime-version:content-disposition;
        bh=UFfXtTKrZE3sZ4dCL6KSsXcB1k5xHExvKKot62Zj5Xg=;
        b=JJv3b+662fLOp0RGiKZIz7UudjJmHyWixZhOphdL2TChuAkyrqaLGun+H0ZF/IqkSi
         T2X210VINskT+RnIwhuBGKaRdseEBf47P6hVaNn38SNypgaq/1oOM2FRTuh4wcGCxcrm
         wL94AUokf+wIqCZfzd94RPbYDPjKkJVu3j6aI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:date:from:to:subject:message-id:mime-version
         :content-disposition;
        bh=UFfXtTKrZE3sZ4dCL6KSsXcB1k5xHExvKKot62Zj5Xg=;
        b=4Coe6yd/uz7rTyNNp5NZeYaG0fOF5oXMQawuMwrk1rsw0HKrUXR30XZ8RfR1SXVlli
         3R67jXvGkl6iTA06787nuYiCHO3bTbMecbByCr2zlHhdvTYc62VPIcNmYcLQydcaP+3M
         rgKQQOT7kV0FMZqyBpEvsejoBEX7W7ZqsTR3gkAUzXgnR04FZBQfqyQlBxbEkWvDu75F
         hM7I7utkLy9lVpWUe08vb0PC5BUSFbsRBq8uJUREZoV9sSqI4yPEA06a/Y6tpwGJnymy
         sY9ssw5x7gusZTBWw61xtkzbqOKhp7VQ745ce3fMt0UkR5nWhsvVwKlM43A4KYjCit4c
         cNTQ==
X-Gm-Message-State: AOAM533ZC36P2tmtnWdBjAZAPsslVm5mJ/GJOq76tQE1Jtv3XZZO0nfZ
	vS25SnXzzFsH+qhANUJKJdJgTfObVhEV3g==
X-Google-Smtp-Source: ABdhPJxV4PYHFhVNam6M6NFNhywpDn/xlLAPeEqLniJI2MtlgrFnOGnvdY6v+/BuPWd6aOv4u7sWDA==
X-Received: by 2002:a05:6e02:2146:: with SMTP id d6mr279423ilv.145.1637354958170;
        Fri, 19 Nov 2021 12:49:18 -0800 (PST)
Received: from meerkat.local (bras-base-mtrlpq5031w-grc-32-216-209-220-181.dsl.bell.ca. [216.209.220.181])
        by smtp.gmail.com with ESMTPSA id t188sm464062iof.5.2021.11.19.12.49.17
        for <meta@public-inbox.org>
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Fri, 19 Nov 2021 12:49:17 -0800 (PST)
Date: Fri, 19 Nov 2021 15:49:16 -0500
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: RFC: should lei inject its own "Received:" header?
Message-ID: <20211119204916.grergcuzj5gcic6c@meerkat.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

Hello:

I wonder if lei should inject its own "received"-like header on writing to a
maildir/imap target -- to indicate where the copy of the email came from. I
don't think it should use the actual Received: header, as this may cause some
weird SPF/DMARC issues, but perhaps something like:

    X-Lei-Received: from https://lore.kernel.org/all/; Fri, 19 Nov 2021 14:32:44 -0500

Just a random thought.

-K