RE: Delayed email (sent through QtmmSendMail, either directly or via MMail)

You may want to unredact these 2 mail server names (Received: by, and X-Received: by)

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)

As this would appear to be where the <REDACTED as probably irrelevant> problem lies. 😊

As has already been said, email is an asynchronous service.

Either the X-Received mail server has sat on your email for some reason or the Received mail server has been too busy or off line or something.

Given
1) the likelihood that both of these mail servers are not in your direct control, and,
2) the possibility that the condition was transient,

probably all you can do is request mail logs from both for the relevant time period, along with their retry settings etc.

Good luck getting a response from those responsible.

Regards,

Kevin Wright

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert
Sent: Wednesday, 27 February 2019 5:21 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Delayed email (sent through QtmmSendMail, either directly or via MMail)

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.