delayed emails
Discussion
Ha sanyone any idea why emails from one paricular source can take up to 3 days to eventually arrive. When they do arrive they are alsways marked as being sent in th eearly hours of the morning.
The same email copied in to my son at a different address always arrive promptly, as do all my other emails.
I use bt openworld broadband. (or whatever they call it today!)
The same email copied in to my son at a different address always arrive promptly, as do all my other emails.
I use bt openworld broadband. (or whatever they call it today!)
your and your sons accounts both with the same ISP ?
if not, might simply be your ISP is taking your mail servers down early in the morning for maintainence.
IF a mail is delayed, typically the sender will recieve an error report, detailing the fact its been delayed, and why.
Might also be your mailbox is full.. but typically thats a terminal error.
if not, might simply be your ISP is taking your mail servers down early in the morning for maintainence.
IF a mail is delayed, typically the sender will recieve an error report, detailing the fact its been delayed, and why.
Might also be your mailbox is full.. but typically thats a terminal error.
No I dont think its any of those things. Its really strange.
I have a bout 3 accounts - BTinternet, tesco.net and beeb.net.
All my emails from whatever source and to whichever account I have always arrive pretty much instantly.
However emails from this pal of mine generally arrive up to 3 days later, and generally indicate that he sent them at some daft time of the early morning.
The identical message, cc'd to my son (or cc'd to me after being sent to my son) arrive in the normal way to his Claranet pop mail account.
The account which arrive late is to my btinternet account which otherwise performs faultlessly.
Conversley, emails which I send to my pal arrive to him in the normal time frame as you would expect.
He never gets any error messages about his sent emails.
It doesn't appear to happen to any of his other sent emails, just mine. Typical!
Very strange.
I have a bout 3 accounts - BTinternet, tesco.net and beeb.net.
All my emails from whatever source and to whichever account I have always arrive pretty much instantly.
However emails from this pal of mine generally arrive up to 3 days later, and generally indicate that he sent them at some daft time of the early morning.
The identical message, cc'd to my son (or cc'd to me after being sent to my son) arrive in the normal way to his Claranet pop mail account.
The account which arrive late is to my btinternet account which otherwise performs faultlessly.
Conversley, emails which I send to my pal arrive to him in the normal time frame as you would expect.
He never gets any error messages about his sent emails.
It doesn't appear to happen to any of his other sent emails, just mine. Typical!
Very strange.
Assuming you are using outlook or outlook express to view your email..
For Outlook try right clicking on the email, and choosing Options. Here you will see "Internet Headers"
In Express, right click the message, Properties - Details
Paste the entire contents of this bit onto here and I (or no doubt someone else) may be able to tell you where the delay is.
Simply put each mail server that the mail passes through should add a received header which contains a number of pieces of information. One of these will likely be the date and time stamp. By working from the bottom up and looking at the date and time stamp in each received header, you can identify at which point the delay came.
Whether this gets you any closer to solving the problem is another thing, but pinning down the location of the delay is the first step in finding the cause.
Here's an example of a message from our web server - you can see that there are timestamps in each Received header:
Received: from [217.8.240.103] by mail.skinfull.co.uk (GMS
10.02.3267/AB0000.00.cbe4b227) with ESMTP id zqwaqiaa for
xxx@skinfull.co.uk; Mon, 27 Sep 2004 14:22:06 +0100
Received: from [217.8.240.20] (helo=kilo.rb.xcalibre.co.uk)
by foxy.xcalibre.co.uk with esmtp (Exim 3.36 #1)
id 1CBvKK-0004a6-00; Mon, 27 Sep 2004 14:14:00 +0100
What this tells me is that assuming the time on both servers is exactly the same, then it took 6 minutes and 6 seconds to send this email.
For Outlook try right clicking on the email, and choosing Options. Here you will see "Internet Headers"
In Express, right click the message, Properties - Details
Paste the entire contents of this bit onto here and I (or no doubt someone else) may be able to tell you where the delay is.
Simply put each mail server that the mail passes through should add a received header which contains a number of pieces of information. One of these will likely be the date and time stamp. By working from the bottom up and looking at the date and time stamp in each received header, you can identify at which point the delay came.
Whether this gets you any closer to solving the problem is another thing, but pinning down the location of the delay is the first step in finding the cause.
Here's an example of a message from our web server - you can see that there are timestamps in each Received header:
Received: from [217.8.240.103] by mail.skinfull.co.uk (GMS
10.02.3267/AB0000.00.cbe4b227) with ESMTP id zqwaqiaa for
xxx@skinfull.co.uk; Mon, 27 Sep 2004 14:22:06 +0100
Received: from [217.8.240.20] (helo=kilo.rb.xcalibre.co.uk)
by foxy.xcalibre.co.uk with esmtp (Exim 3.36 #1)
id 1CBvKK-0004a6-00; Mon, 27 Sep 2004 14:14:00 +0100
What this tells me is that assuming the time on both servers is exactly the same, then it took 6 minutes and 6 seconds to send this email.
Here it is!
X-Apparently-To: andygo@btinternet.com via 217.12.13.14; Sun, 03 Oct 2004 02:12:18 +0000
X-Originating-IP: [193.113.154.33]
Return-Path: <mark.chadwick@northerninteractive.co.uk>
Received: from 193.113.154.33 (HELO c2bapps17.btconnect.com) (193.113.154.33)
by mta802.mail.ukl.yahoo.com with SMTP; Sun, 03 Oct 2004 02:12:18 +0000
Received: from Koopid1 (actually host 192.91.35.217.in-addr.arpa) by dswu194 with SMTP-CUST (XT-PP); Thu, 30 Sep 2004 12:23:09 +0100
Message-ID: <03cc01c4a6e0$094309d0$0f10a8c0@Koopid1>
From: "Mark Chadwick" <mark.chadwick@northerninteractive.co.uk>
To: "Andy Gough" <andygo@btinternet.com>
References: <000601c4a627$25dc0c90$9400a8c0@laptop> <003201c4a627$d01af720$0f10a8c0@Koopid1> <000801c4a646$c3ad69e0$0100a8c0@main>
Subject: Re: WHT
Date: Thu, 30 Sep 2004 12:24:22 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_03C9_01C4A6E8.6AB05120"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
As you can see, it was sent at 12.24 on 30th Sept.
I recieved it on sunday 3rd oct @ 02.12
does that mean BT have been hanging on to it?
X-Apparently-To: andygo@btinternet.com via 217.12.13.14; Sun, 03 Oct 2004 02:12:18 +0000
X-Originating-IP: [193.113.154.33]
Return-Path: <mark.chadwick@northerninteractive.co.uk>
Received: from 193.113.154.33 (HELO c2bapps17.btconnect.com) (193.113.154.33)
by mta802.mail.ukl.yahoo.com with SMTP; Sun, 03 Oct 2004 02:12:18 +0000
Received: from Koopid1 (actually host 192.91.35.217.in-addr.arpa) by dswu194 with SMTP-CUST (XT-PP); Thu, 30 Sep 2004 12:23:09 +0100
Message-ID: <03cc01c4a6e0$094309d0$0f10a8c0@Koopid1>
From: "Mark Chadwick" <mark.chadwick@northerninteractive.co.uk>
To: "Andy Gough" <andygo@btinternet.com>
References: <000601c4a627$25dc0c90$9400a8c0@laptop> <003201c4a627$d01af720$0f10a8c0@Koopid1> <000801c4a646$c3ad69e0$0100a8c0@main>
Subject: Re: WHT
Date: Thu, 30 Sep 2004 12:24:22 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_03C9_01C4A6E8.6AB05120"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
As you can see, it was sent at 12.24 on 30th Sept.
I recieved it on sunday 3rd oct @ 02.12
does that mean BT have been hanging on to it?
andygo said:
does that mean BT have been hanging on to it?
I would say yes. Again, assuming that the timestamps are correct, here's the relevant bit.
Received: from 193.113.154.33 (HELO c2bapps17.btconnect.com) (193.113.154.33)
by mta802.mail.ukl.yahoo.com with SMTP; Sun, 03 Oct 2004 02:12:18 +0000
Received: from Koopid1 (actually host 192.91.35.217.in-addr.arpa) by dswu194 with SMTP-CUST (XT-PP); Thu, 30 Sep 2004 12:23:09 +0100
So you can see that it arrived on the BT server and then sat there for days. If I had to guess I would say that the sheer volume of mail that is queued for Yahoo is causing the delay.
We see this a lot for some customers - massive queues which can't be processed quickly enough because the big providers like yahoo and hotmail are so strict that they will drop connections at the first opportunity, forcing a re-queue. No surprise to see BT suffering from this. Might still be worth taking the above header and emailing BT support though.
Ben
The sender is using bt connect to dial up isn't he - sending via their mailserver.
It's certainly the bt connect mailserver holding onto the mail for too long.. although why it only happens in your case has me stumped. If all bt connect customers were getting this delay when sending emails to all bt internet customers you'd think someone would have noticed by now (even if it is run by Yahoo)
Get him to dial up with someone else
It's certainly the bt connect mailserver holding onto the mail for too long.. although why it only happens in your case has me stumped. If all bt connect customers were getting this delay when sending emails to all bt internet customers you'd think someone would have noticed by now (even if it is run by Yahoo)
Get him to dial up with someone else
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff