More email delays?

[#1]

[off-topic]
The code tag problem is a bug with using Firefox. I've posted a fix for it, hoping one of the web folks will find it soon Major pain in the backside.
[/off-topic]

[#2]

pm colin

[#3]

The client was using Thunderbird and we did check the Sent folder.
After re-stating the Router we sent some test messages and these got through ok. We then back-tracked over the Sent folders list and re-sent those messages that we thought hadnt been delivered.
Since re-starting the Router,  there has been no reported loss of  sent messages.
The client indicated that the loss of messages had probably started around a week ago, it took a while to discover that they had gone missing. The Router was re-started on Wednesday of this week.
My client is happy that emails are now getting through but I am still concerned that it took a Router re-start to get the emails  sent through.

[#4]

FWIW, I still haven't received the e-mail I forwarded myself Friday evening.

[#5]

My mother in law (we are both Plusnet customers) complained that her email was unreliable. Sometime she couldn't connect to relay to send mail, although web sites were working. I sent an email from her, back to herself. Nothing complex there, simply Plusnet to Plusnet. As you can see it took 22 minutes.

Quote

Delivery-date: Fri, 12 Oct 2007 18:41:51 +0100 Received: from ptb-relay03.plus.net ([212.159.14.214])       by pih-sunmxcore19.plus.net with esmtp (PlusNet MXCore v2.00) id 1IgOWF-0007k0-8y       for mail@xxxx.plus.com; Fri, 12 Oct 2007 18:41:51 +0100 Received: from xxxx.plus.com ([84.92.59.65] helo=[127.0.0.1])     by ptb-relay03.plus.net with esmtp (Exim) id 1IgOAy-0007zD-Di     for mail@xxxx.plus.com; Fri, 12 Oct 2007 18:19:54 +0100 Message-ID: <470FACB9.2060703@xxxx.plus.com> Date: Fri, 12 Oct 2007 18:19:53 +0100 From: XXX XXX <mail@xxxx.plus.com>

I don't know enough to know whether the delay is relay too busy to send it to core, or core taking a while to accept the connection.
Chris

[#6]

Laughably even a response from JTN to tell me they are looking into the problem on their network took almost 14 hours to get me without leaving the Plusnet network.
Envelope-to: xxxxxx@metronet.co.uk
Delivery-date: Sat, 13 Oct 2007 00:16:24 +0100
Received: from just-the-name.co.uk ([213.162.97.161] helo=mail.just-the-name.co.uk)
  by pih-sunmxcore18.plus.net with esmtp (PlusNet MXCore v2.00) id 1IgTjz-00070k-Jv
  for xxxxxxx@metronet.co.uk; Sat, 13 Oct 2007 00:16:23 +0100
Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132])
by mail.just-the-name.co.uk (Postfix) with ESMTP id 3D056406C3B
for <xxxxxxxx@xxxxxxx.co.uk>; Fri, 12 Oct 2007 10:43:53 +0100 (BST)
Received: from [212.159.0.11] (helo=[84.93.219.126])
by pih-relay05.plus.net with esmtp (Exim) id 1IgH3i-00007m-1S
for xxxxxxx@xxxxxxx.co.uk; Fri, 12 Oct 2007 10:43:54 +0100
Message-ID: <470F40EF.9020305@just-the-name.co.uk>
Date: Fri, 12 Oct 2007 10:39:59 +0100
From: xxxxxxxx <support@just-the-name.co.uk>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: xxxxxxx <xxxxxxxx@xxxxxxx.co.uk>
Subject: Re: Mailbox at xxxxxxxx@xxxxxxx.co.uk
References: <CA7952C9D82A447286C624D9867B02EF@xxxxxxxPC>
In-Reply-To: <CA7952C9D82A447286C624D9867B02EF@xxxxxxxPC>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

[#7]

Emails getting delayed by about an hour from and into my metronet account this morning. I might have to switch away from using metronet email.....

[#8]

After several weeks of problems, the last 24hours have seen a marked improvement.

[#9]

It's now Monday lunchtime, and I've just received an email that was sent to me, from a freeserve email account, late on Thursday night - i.e a 3.5 day delay.
I'm not clear as to whether the cause of the bottleneck lies with Freeserve, or with Plusnet.
I'd appreciate it someone could take a look at this, and see whether if it's indicative of continuing problems, can be explained, by a problem which is now fixed, or is attributal to Freeserve.
The headers are below (edited to remove some addresses).
Thanks in advance,  John

Quote

Delivery-date: Mon, 15 Oct 2007 12:23:09 +0100 Received: from smtp5.freeserve.com ([193.252.22.159])           by pih-sunmxcore18.plus.net with esmtp (PlusNet MXCore v2.00) id 1IhO2O-0006js-G1           for *@*.plus.com; Mon, 15 Oct 2007 12:23:09 +0100 Received: from smtp5.freeserve.com (mwinf3429 [10.232.11.129])         by mwinf3405.me.freeserve.com (SMTP Server) with ESMTP id BBADE1C9E7FC         for <*.*.plus.com>; Thu, 11 Oct 2007 23:42:35 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1])         by mwinf3429.me.freeserve.com (SMTP Server) with ESMTP id 79DF11C00086         for <*.*.plus.com>; Thu, 11 Oct 2007 23:42:15 +0200 (CEST) Received: from PEWTOR (modem-1348.cheetah.dialup.pol.co.uk [217.134.101.68])         by mwinf3429.me.freeserve.com (SMTP Server) with SMTP id 249781C00084         for <*.*.plus.com>; Thu, 11 Oct 2007 23:41:35 +0200 (CEST)

[#10]

Hi John,
Looks like the email was sat on this server:

Quote

Received: from smtp5.freeserve.com (mwinf3429 [10.232.11.129])         by mwinf3405.me.freeserve.com (SMTP Server) with ESMTP id BBADE1C9E7FC         for <*.*.plus.com>; Thu, 11 Oct 2007 23:42:35 +0200 (CEST)

The reason it was delayed for so long could be down to a problem at Freeserve's side, or it may have been that our mail delivery platform was refusing the connection from Freeserve - We wouldn't really know without trawling our logs.
I personally think it's something to do with this. On Thursday when the email was sent we had a number of ACL rules in place designed to temporarily defer messages that didn't meet certain DNS criteria. For one reason or another I suspect that our mail platform was rejecting this email from Freeserve. The Freeserve servers will have kept on attempting delivery but at less frequent intervals following each failed attempt.
We removed the ACL rules on Friday which allowed the email to come through.

[#11]

Thanks for the feedback, Bob
John

[#12]

Quote

We removed the ACL rules on Friday which allowed the email to come through.

Having trawled through a large number of headers, before seeing the post above, there has been no delay accessing PlusNet servers (from my host) since 1800bst on Friday, which may tie in with what Bob posted.

Quote

The reason it was delayed for so long could be down to a problem at Freeserve's side, or it may have been that our mail delivery platform was refusing the connection from Freeserve

With the delays arising for a number of hosts, I would have thought it reasonable to suggest that the problem was with PlusNet.

[#13]

I'm inclined to agree with canford, seeing as the e-mail I forwarded from a PlusNet account to a PlusNet account on Thursday evening still hasn't arrived. Although having said that, I'm beginning to suspect that it's simply not going to turn up at all now. (Though the question then is, why?) And I also notice that I was sent an e-mail (not from PlusNet) at about 6:50pm this evening, which is still yet to turn up too...

[#14]

Be3G, did that email come through? Where did the headers show the delay?

[#15]

Sorry for late reply; been busy for the past couple of days... but nope, that e-mail's still not turned up, so it really does look like it's just vanished in to thin air.