以下电子邮件被标记为在 8 月 15 日发送，但在 9 月 6 日收到。
除了第一个之外，电子邮件上的所有日期戳都是 9 月 6 日（有些是 7 日，但这是因为接收服务器是 PDT 而不是 GMT）。
发件人声称这封电子邮件是在 8 月 15 日，几乎三周前从他们的机器发送的。这是真的吗？有什么办法让它离开他们的机器然后卡在某个地方直到 6 号？
第一封电子邮件：所有时间戳的日期都在“发送”日期后三周
Delivered-To: xxxxxxxx
Received: by 10.231.4.202 with SMTP id 10cs144069ibs;
Tue, 6 Sep 2011 20:25:32 -0700 (PDT)
Received: by 10.227.152.129 with SMTP id g1mr5802672wbw.56.1315365931065;
Tue, 06 Sep 2011 20:25:31 -0700 (PDT)
Return-Path: <xxxxxxxx>
Received: from coumta04.netbenefit.co.uk (coumta04.netbenefit.co.uk [95.130.76.115])
by mx.google.com with ESMTP id 21si9249722wbw.107.2011.09.06.20.25.29;
Tue, 06 Sep 2011 20:25:30 -0700 (PDT)
Received-SPF: neutral (google.com: 95.130.76.115 is neither permitted nor denied by best guess record for domain of xxxxxxxx) client-ip=95.130.76.115;
Authentication-Results: mx.google.com; spf=neutral (google.com: 95.130.76.115 is neither permitted nor denied by best guess record for domain of xxxxxxxx) smtp.mail=xxxxxxxx
Received: from [84.252.254.11] (port=1257 helo=xxxxxxxx)
by coumta04.netbenefit.co.uk with esmtp (NBT 4.72 2)
id 1R18lR-0001SR-DZ
for xxxxxxxx; Wed, 07 Sep 2011 04:25:29 +0100
Return-Receipt-To: "xxxxxxxx" <xxxxxxxx>
Subject: xxxxxxxx
Date: Mon, 15 Aug 2011 15:51:10 +0100
Message-ID: <xxxxxxxx>
X-MS-Has-Attach: yes
MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
boundary="----_=_NextPart_001_01CC5B5A.C52AC300"
X-MS-TNEF-Correlator:
Thread-Topic: xxxxxxxx
Thread-Index: xxxxxxxx
Disposition-Notification-To: xxxxxxxx
Content-class: urn:content-classes:message
From: xxxxxxxx
X-MimeOLE: Produced By Microsoft Exchange V6.5
To: xxxxxxxx
X-NB-Virus-Scan: virus-free
X-Originally-To: xxxxxxxx
This is a multi-part message in MIME format.
------_=_NextPart_001_01CC5B5A.C52AC300
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01CC5B5A.C52AC300"
------_=_NextPart_002_01CC5B5A.C52AC300
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
xxxxxxxx
------_=_NextPart_002_01CC5B5A.C52AC300
xxxxxxxx
------_=_NextPart_002_01CC5B5A.C52AC300--
------_=_NextPart_001_01CC5B5A.C52AC300
Content-Type: image/jpeg;
name="xxxxxxxx"
Content-Transfer-Encoding: base64
Content-Description: xxxxxxxx
Content-Location: xxxxxxxx
xxxxxxxx
------_=_NextPart_001_01CC5B5A.C52AC300--
编辑
第二封电子邮件与第一封电子邮件同时送达。两封电子邮件来自同一家公司，但来自不同的人，可能是该公司的计算机。虽然一个可能的答案是个人忘记按“发送和接收”三周或电子邮件被 Outlook 捕获，但收到两封此类电子邮件的可能性要小得多。
同一公司不同人同时发送的第二封电子邮件（2 周后）
在此期间，该公司没有声称或抱怨任何互联网中断。请注意，第二封电子邮件的第一跳比前一封电子邮件的第一跳早 7 秒，而“发送日期”显然是两周后：
Delivered-To: xxxxxxxx
Received: by 10.231.4.202 with SMTP id 10cs144068ibs;
Tue, 6 Sep 2011 20:25:26 -0700 (PDT)
Received: by 10.216.229.88 with SMTP id g66mr2963523weq.9.1315365924837;
Tue, 06 Sep 2011 20:25:24 -0700 (PDT)
Return-Path: <xxxxxxxx>
Received: from coumta04.netbenefit.co.uk (coumta04.netbenefit.co.uk [95.130.76.115])
by mx.google.com with ESMTP id u35si8835621weq.122.2011.09.06.20.25.23;
Tue, 06 Sep 2011 20:25:23 -0700 (PDT)
Received-SPF: neutral (google.com: 95.130.76.115 is neither permitted nor denied by best guess record for domain of xxxxxxxx) client-ip=95.130.76.115;
Authentication-Results: mx.google.com; spf=neutral (google.com: 95.130.76.115 is neither permitted nor denied by best guess record for domain of xxxxxxxx) smtp.mail=xxxxxxxx
Received: from [84.252.254.11] (port=1257 helo=xxxxxxxx)
by coumta04.netbenefit.co.uk with esmtp (NBT 4.72 2)
id 1R18lO-0001SR-G0
for xxxxxxxx; Wed, 07 Sep 2011 04:25:23 +0100
Subject: xxxxxxxx
Date: Tue, 30 Aug 2011 10:49:00 +0100
Message-ID: <xxxxxxxx>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
MIME-Version: 1.0
Content-Type: multipart/related;
type="multipart/alternative";
boundary="----_=_NextPart_001_01CC66FA.0B9BFD72"
Thread-Topic: xxxxxxxx
Thread-Index: Acxm+gtdtV3BSonSR826xyTFQoiE9w==
From: "xxxxxxxx" <xxxxxxxx>
Content-class: urn:content-classes:message
To: <xxxxxxxx>
X-MimeOLE: Produced By Microsoft Exchange V6.5
Cc: "xxxxxxxx" <xxxxxxxx>
X-NB-Virus-Scan: virus-free
X-Originally-To: xxxxxxxx
This is a multi-part message in MIME format.
------_=_NextPart_001_01CC66FA.0B9BFD72
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01CC66FA.0B9BFD72"
------_=_NextPart_002_01CC66FA.0B9BFD72
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
xxxxxxxx
------_=_NextPart_002_01CC66FA.0B9BFD72
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
xxxxxxxx
------_=_NextPart_002_01CC66FA.0B9BFD72--
xxxxxxxx
------_=_NextPart_001_01CC66FA.0B9BFD72
Content-Type: image/jpeg;
name="xxxxxxxx"
Content-Transfer-Encoding: base64
Content-Description: xxxxxxxx
Content-Location: xxxxxxxx
xxxxxxxx
------_=_NextPart_001_01CC66FA.0B9BFD72--
我知道更改计算机时钟会导致 Outlook 提供与此相同的外发邮戳，但我想知道是否有任何合理的理由。
不，这是不可能的。至少不是真的。
Received: from [84.252.254.11] (port=1257 helo=xxxxxxxx)
by coumta04.netbenefit.co.uk with esmtp (NBT 4.72 2)
id 1R18lR-0001SR-DZ
for xxxxxxxx; Wed, 07 Sep 2011 04:25:29 +0100
Date: Mon, 15 Aug 2011 15:51:10 +0100
这表明邮件是在 8 月份写的。可能是伪造的，但有可能，让我们假设这真的是在八月写的。但是第一个收到的行表示第一个收到邮件的真实邮件服务器。这是在九月。这条线也可以伪造，但谁来伪造他呢？
那么可能发生了什么？
无论如何（可能是我没有想到的场景），邮件在 9 月（或服务器认为是 9 月）到达了第一台服务器。但问题出在客户端（用户、软件、网络等）。
编辑
或者正如您发现的最后一种情况：第一台服务器已关闭并且根本无法接受邮件。客户端尝试并尝试但直到管理员在 9 月重新启动服务器才成功。或者其他“破坏”第一台接受邮件的服务器的东西。
| 归档时间： |
|
| 查看次数： |
545 次 |
| 最近记录： |