× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 2/25/19, 1:53 PM, Kevin Wright wrote:
I would be looking at the "real" message headers (in outlook they are
called "internet headers") for both a delayed and an undelayed email
to see if there is any clue there.

I found something. I've double-quoted the notable bits, and redacted certain information that appears either sensitive, irrelevant, or both.

My non-delayed email:

Delivered-To: jamesl@xxxxxxxxxxxxxxxxx
Received: by <REDACTED as probably irrelevant>
Mon, 25 Feb 2019 08:02:04 -0800 (PST)
X-Google-Smtp-Source: <REDACTED as probably irrelevant>
X-Received: by <REDACTED as probably irrelevant>
Mon, 25 Feb 2019 08:02:03 -0800 (PST)
ARC-Seal: <REDACTED as probably irrelevant>
ARC-Message-Signature: <REDACTED as probably irrelevant>
ARC-Authentication-Results: i=1; mx.google.com;
spf=neutral <details REDACTED>
Return-Path: <info@xxxxxxxxxxxxxxxxx>
Received: from venus.private.touchtonecorp.com <REDACTED>
for <jamesl@xxxxxxxxxxxxxxxxx>;
Mon, 25 Feb 2019 08:02:03 -0800 (PST)
Received-SPF: neutral <REDACTED>
Authentication-Results: mx.google.com;
spf=neutral <REDACTED>
Sender: "info@xxxxxxxxxxxxxxxxx" <info@xxxxxxxxxxxxxxxxx>
Date: Mon, 25 Feb 2019 08:00:08 -0800
From: "info@xxxxxxxxxxxxxxxxx" <info@xxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Message-ID: <2019-02-25-08.00.08.873000@xxxxxxxxxxxxxxxxx>
To: "jamesl@xxxxxxxxxxxxxxxxx" <jamesl@xxxxxxxxxxxxxxxxx>

And the delayed one:

Delivered-To: <REDACTED for privacy>
Received: by <REDACTED as probably irrelevant>
Mon, 25 Feb 2019 08:36:01 -0800 (PST)
X-Google-Smtp-Source: <REDACTED as probably irrelevant>
X-Received: by <REDACTED as probably irrelevant>
Mon, 25 Feb 2019 08:02:04 -0800 (PST)
ARC-Seal: <REDACTED as probably irrelevant>
ARC-Message-Signature: <REDACTED as probably irrelevant>
ARC-Authentication-Results: i=1; mx.google.com;
spf=neutral <details REDACTED>
Return-Path: <info@xxxxxxxxxxxxxxxxx>
Received: from venus.private.touchtonecorp.com <REDACTED>
for <REDACTED>;
Mon, 25 Feb 2019 08:02:04 -0800 (PST)
Received-SPF: neutral <REDACTED>
Authentication-Results: mx.google.com;
spf=neutral <REDACTED>
Sender: "info@xxxxxxxxxxxxxxxxx" <info@xxxxxxxxxxxxxxxxx>
Date: Sun, 25 Feb 2019 08:00:10 -0800
From: "info@xxxxxxxxxxxxxxxxx" <info@xxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Message-ID: <2019-02-25-08.00.10.017000@xxxxxxxxxxxxxxxxx>
To: "<REDACTED for privacy>" <REDACTED for privacy>

Notice how on the delayed message, the date on the "Received: by" header, second from the top, is the ONLY date stamp to show the long delay.

That's definitely something; I'm not sure what it means. But it seems to be the most significant difference.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.