-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Gerd,
On 13 August 2000 at 11:45:42 GMT +0200 (which was 10:45 where I
live) [EMAIL PROTECTED] wrote and made these points on the subject
of "Replies arrive before originals (was:Re: Strange error message
when sending)":
GE> I can give some details to this problem: it seemes as if it has
GE> sometimes to do with Mark R. Harding's msgs (Sorry, no offence,
GE> Mark).
This has nothing to do with Mark's account. It is to do with the
routing used to reach your domain, which seems to be variable -
possibly because there are multiple MX records for the domain and the
message gets routed to the first domain MX server which responds in
real time. The server will traverse the list of MX servers for the
domain in order of priority until it finds one that will accept the
mail. It seems that one of them is more than slightly sluggish.
GE> I sent these examples OFF-LIST to Curtis (I was't sure whether
GE> this topic is of everyone's interest). He answered:
>>> Any idea ?
ACM>> Nope. Maybe Syafril can help.
GE> Syafril, can you ??
I can tell you from these *exactly* where the blockage occurred:
GE> +++ COPY 1
GE> Received: from mailgate2.cinetic.de by mx03.web.de with smtp
GE> (freemail 4.1.0.0 #62) id m13NWN5-00GZUqa; Sat, 12 Aug 2000 10:10 +0200
^^^^^
Right here - this relay point is ten hours *after* it arrived ....
GE> Received: from relay.xlink.net (relay.xlink.net [193.141.40.4])
GE> by mailgate2.cinetic.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id
AAA02888
GE> for <[EMAIL PROTECTED]>; Sat, 12 Aug 2000 00:12:46 +0200
^^^^^^^^
Here at relay.xlink.net, which had already sat on the message for
two and a half hours since receiving it from the dutaint server ...
GE> Received: from dutaint.com (ns2.dutaint.com [203.130.233.13])
GE> by relay.xlink.net (8.9.3/8.8.7) with ESMTP id VAA01593
GE> for <[EMAIL PROTECTED]>; Fri, 11 Aug 2000 21:38:30 +0200 (MET DST)
^^^^^^^^
At this time. Of course, this is assuming that the clocks on the
servers involved are correct.
GE> Received: from postbox.ee.ed.ac.uk by dutaint.com
GE> with SMTP (MDaemon.v3.5.0c.R)
GE> for <[EMAIL PROTECTED]>; Sat, 12 Aug 2000 02:36:02 +0700
^^^^^^^^
Take away 7 and add 2 to give a time of 21:36 in MET DST +0002 format
which states that relay.xlink.net got the message a mere *two minutes*
after it left Mark's site...
GE> Received: from pcv08.ee.ed.ac.uk (pcv08 [129.215.232.118])
GE> by postbox.ee.ed.ac.uk (8.9.1/8.9.1) with ESMTP id UAA05221
GE> for <[EMAIL PROTECTED]>; Fri, 11 Aug 2000 20:35:45 +0100 (BST)
Which was only one minute after he sent it.
GE> ++ COPY 2
Now, this message underwent a *completely* different routing and
relay.xlink.net was not involved giving us the following timings...
GE> Received: from dutaint.com by mx04.web.de with smtp
GE> (freemail 4.1.0.0 #61) id m13NKqh-006qz0a; Fri, 11 Aug 2000 21:52 +0200
^^^^^
This is a mere two minutes after it left the dutaint server ...
GE> Received: from teleute.rpglink.com by dutaint.com
GE> with SMTP (MDaemon.v3.5.0c.R)
GE> for <[EMAIL PROTECTED]>; Sat, 12 Aug 2000 02:50:01 +0700
^^^^^^^^
Take away 7 and add 2 to give a time of 21:50 in MET DST +0002 format
as the time that it arrived at dutaint from rpgliink...
GE> Received: from antelope.it.earthlink.net [207.217.90.52]
GE> by teleute.rpglink.com with esmtp (Exim 3.12 #1 (Debian))
GE> id 13NKjN-0004sG-00; Fri, 11 Aug 2000 12:44:37 -0700
Which is six minutes after rpglink got it in the first place.
IOW: I'd have a word with your ISP.
I agree that this is not always the case. The "retry queue" has had a
mention in this thread and I can state what this is here and now. If
all MX servers (see above) fail to respond after a fixed retry count
(x times for each server in the MX list for the domain - I have my
server set at three, I think the default is four) the message fails
the immediate delivery and is placed in the retry queue. This queue is
processed at regular intervals - usually four hourly ... I don't know
what Syafril has defaulted ours to - for around 4 days. After four
days, the server will inform the list manager (in the case of list
traffic) of the permanent delivery failure. This is the retry queue
logic. It doesn't apply to the example you have given - there is no
appreciable delay between the dutaint server receiving the original
message and the relay servers on the other side accepting the message
for forward delivery.
HTH
- --
Cheers,
.\\arck
Marck D. Pearlstone, Consultant Software Engineer
Moderator TBUDL / TBBETA
www: http://www.silverstones.com
PGP key: <mailto:[EMAIL PROTECTED]?Body=GET%20MARCKKEY>
*-----------------------------------------------
| Using The Bat! 1.46 Beta/3 S/N 14F4B4B2
| under Windows 98 4.10 Build 1998
*-----------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2i
iQA/AwUBOZaErznkJKuSnc2gEQK3dwCeJY4ztenwfh5VAt882skRLE8fK5EAn31H
F1Flrj4UsIf7l9FYNb+Yl5gm
=Y2VH
-----END PGP SIGNATURE-----
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
