Problems with delayed emails

[Sgt. Slaughter]

That's possible. I just got another one from earlier.

From Officer Resource Thu May 7 19:18:44 2009
Return-Path: <officerresource@yahoo.com>
Authentication-Results: mta601.mail.mud.yahoo.com from=yahoo.com; domainkeys=neutral (no sig)
Received: from 127.0.0.1 (EHLO vps.officerresource.com) (216.227.216.91)
by mta601.mail.mud.yahoo.com with SMTP; Thu, 07 May 2009 19:49:12 -0700
Received: (qmail 13864 invoked by uid 48); 7 May 2009 19:18:44 -0700
Date: 7 May 2009 19:18:44 -0700
To: nospam at yahoo.com
Subject: Reply to thread 'Knock Knock.'
From: "Officer Resource" <officerresource at yahoo.com>
Auto-Submitted: auto-generated
Message-ID: <20090508021842.a80578292095@o fficerresource.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Length: 923

[Sgt. Slaughter]

I'll just leave it at this:

It takes a long damn time for the email to get from the Upper Midwest all the way down here to Arizona!!!!

[MacLean]

I'll just leave it at this:

It takes a long damn time for the email to get from the Upper Midwest all the way down here to Arizona!!!!

I concur with Xiphos, the headers indicate the email is being sent rapidly.

Somewhere in between here and you there is an issue. I bet you could find it if you could run a tracert between your mail server and ours.

Since you can't do that, take a gander at a tracert between you and your mail server, and between you and here. Somewhere there will be a slow hop.

[MacLean]

I'll just leave it at this:

It takes a long damn time for the email to get from the Upper Midwest all the way down here to Arizona!!!!

It isn't technically coming from the upper midwest.

[Terminator]

I concur with Xiphos, the headers indicate the email is being sent rapidly.

I also concur, and I'm a computer geek.