Gmail delays in "Instant" notifications

[+Geofellas]

Tue, 06 Mar 2007 10:11:05 -0800 (PST)

Return-Path: <noreply@geocaching.com>

Received: from signal.Groundspeak.com (signal.Groundspeak.com [66.150.167.157])

by mx.google.com with ESMTP id a8si20247477poa.2007.03.06.10.11.05;

Tue, 06 Mar 2007 10:11:05 -0800 (PST)

Received-SPF: pass (google.com: domain of noreply@geocaching.com designates 66.150.167.157 as permitted sender)

Received: from hal.Groundspeak.com (hal.Groundspeak.com [66.150.167.136])

by signal.Groundspeak.com (Postfix) with ESMTP id 53A49246FE

for <xxxxxx@gmail.com>; Mon, 5 Mar 2007 13:17:36 -0800 (PST)

Received: from mail pickup service by hal.Groundspeak.com with Microsoft SMTPSVC;

Mon, 5 Mar 2007 13:17:36 -0800

 

The above extract from the headers of a recent "instant" notification seems to indicate a delay of almost 21 hours in the e-mail moving from signal.Groundspeak.com to mx.google.com (i.e. gmail)

[+Prime Suspect]

Starting sometime yesterday, an email in queue on our mail server became corrupted and caused mail delivery to slow to a crawl. This created a large backlog of email and affected all mail destinations.

 

Early this morning I found and deleted the corrupted message and mail began flowing again. Most mail for highly performing destinations such Gmail should already have been delivered. Mail to Yahoo and other domins which either throttle us or have slower delivery rates may take a few more hours to receive all their backlogged email.

 

At this time, I do not know what caused the corrupted email, but I'm continuing to investigate.

 

signalsmile.gif Elias

 

Read it here.

[+gnbrotz]

It wasn't just instant notifications. It also affected watchlist notices, forum subscriptions, and forum PM notifications. Pretty much an all-around problem this time.