Here's the top few trace headers on a message I recently received from an IETF
server,
The two Delivered-To headers are due to the way qmail handles virtual domains.
It's been doing it that way for over 20 years, so it's definitely existing
practice.
Once again, I don't think we have anything to say about the order of the headers
beyond noting that Delivered-To is yet another trace header.
R's,
John
Return-Path: <jay(_at_)ietf(_dot_)org>
Delivered-To: johnl(_at_)gal(_dot_)iecc(_dot_)com
Received: (qmail 6459 invoked by uid 1014); 28 Jan 2021 01:14:45 -0000
Delivered-To: virtual-standcore-john(_dot_)levine(_at_)standcore(_dot_)com
Received: (qmail 6457 invoked from network); 28 Jan 2021 01:14:45 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on gal.iecc.com
X-Spam-Level:
X-Spam-Status: No, score=-1.4 required=4.4 tests=BAYES_00,KAM_NUMSUBJECT,
SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.4
Authentication-Results: iecc.com; spf=pass spf.mailfrom=jay(_at_)ietf(_dot_)org
spf.helo=mail.ietf.org smtp.remote-ip="4.31.198.44"; dmarc=pass
header.from=ietf.org polrec.p=none polrec.pct=100
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
by mail1.iecc.com ([64.57.183.56])
with ESMTPS via TCP (port 37853/25) id 669561580
tls TLS1.2_ECDHE_RSA_AES_256_GCM_AEAD; 28 Jan 2021 01:14:44 -0000
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp