Here's an example from pgsql-docs:
Received: from news.tht.net (news.hub.org [216.126.91.242])
by whale.fsr.net (8.9.3/8.9.3) with ESMTP id NAA06518
Thu, 30 Mar 2000 13:14:41 -0800 (PST)
Received: from hub.org (hub.org [216.126.84.1])
by news.tht.net (8.9.3/8.9.3) with SMTP id PAA09679;
Thu, 30 Mar 2000 15:28:45 -0500 (EST)
Received: from thelab.hub.org (nat196.110.mpoweredpc.net [142.177.196.110])
by hub.org (8.9.3/8.9.3) with ESMTP id PAA69404;
Thu, 30 Mar 2000 15:16:44 -0500 (EST)
You sent the message at 20:16 UTC. Mj2 had delivered it to your
MTA by 20:28, and it finally arrived at my ISP at 21:14.
There are two possible problems...the first is that the MTA you're using tends
to have delays during SMTP conversations due to DNS lookups. The second
is that sometimes the conversation between mj_queueserv and mj_queuerun
will time out if the system load is high, and messages will remain
in the Mj2 queue until another request arrives. The second problem
can be ameliorated by increasing the queue timeout in .mj_config
and reinstalling.
Michael
:}
:}okay, here is one report out of many complaints about mj2 vs mj1 ... the
:}list in question here has alot more users on it then the committers, which
:}would make it understandable as to why one is faster then the other ...
:}
:}comments? suggestions?
:}
:}Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
:}Systems Administrator @ hub.org
:}primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Follow-Ups:
References:
|
|
