recently the ratio of "e-mails that work" vs. "e-mails that fail" has
worsened considerably. So much so that now I'm resorting to posting via
the newsgroup :)
Ordinarilly I wouldn't care, but the "problem" only seems to exist for this
one list, so just because it is anomolous, it is really starting to "bug
me" -- I'm curious if it is something to do with the recent list changes
[to reduce "spam"] or a strange misconfiguration of either my computer or
various computer(s) at pacbell [which I've heard have been unreliable as of
late...]
When messages fail, I get the following [about three or four days later, so
I've completely forgotten what I've posted and/or why...]:
This report relates to a message you sent with the following header fields:
Return-path: <[log in to unmask]>
Received: from mta5.snfc21.pbi.net by mta5.snfc21.pbi.net
(iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002))
id <[log in to unmask]>; Mon, 13 Jan 2003 00:47:32 -0800
(PST)
Received: from bigbro ([207.105.40.84])
by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 HotFix 1.6 (built
Oct 18
2002)) with ESMTP id <[log in to unmask]> for
[log in to unmask]; Thu, 09 Jan 2003 11:13:13 -0800 (PST)
Date: Thu, 09 Jan 2003 11:13:10 -0800
From: Tom Emerson <[log in to unmask]>
Subject: Re: [HP3000-L] How to tidy up a stdlist when using IF...ELSE...
In-reply-to: <[log in to unmask]>
To: [log in to unmask]
Message-id: <[log in to unmask]>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
User-Agent: KMail/1.4.3
References: <[log in to unmask]>
Your message is being returned; it has been enqueued and undeliverable for
3 days to the following recipients:
Recipient address: [log in to unmask]
Reason: unable to deliver this message after 3 days
Delivery attempt history for your mail:
Sun, 12 Jan 2003 22:26:28 -0800 (PST)
TCP active open: Failed connect() Error: Connection timed out
[repeats A LOT of times...]
Since there is a "received..." line that gives a pacbell machine such as
mta5.snfc21.pacbell.net or mta6..., and showing that it "came from" bigbro,
I have to presume "it left the building here" OK and the "failed to
connect/connection timed out" messages are being generated on or by the
"mta..." computers. ["bigbro" is the computer I'm sitting at right now --
it is a linux workstation "hiding behind" a NAT/firewall computer at IP
address 207.105.40.84] [my assigned DSL IP address] [also a linux
computer]
So, now I'm very curious: are any other "pacbell" subscribers having
difficulty posting "via e-mail"? If so, are you using "dial up" or do you
have a DSL or better connection? [do we even HAVE any other pacbell
subscribers?]
=====
Note that the above set of headers is what the "delivery failed notice"
contains in the actual message part -- the headers of the message as it
arrives on my machine begin with:
Received: from mtac3.prodigy.net by mailapps1 with SMTP; Mon, 13 Jan 2003
03:50:14 -0500
X-Originating-IP: [206.13.28.241]
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
by mtac3.prodigy.net (8.12.3/8.12.3) with ESMTP id h0D8o97X025477
for <[log in to unmask]>; Mon, 13 Jan 2003 02:50:13 -0600 (CST)
Received: from process-daemon.mta5.snfc21.pbi.net by mta5.snfc21.pbi.net
(iPlanet Messaging Server 5.1 HotFix 1.6 (built Oct 18 2002))
id <[log in to unmask]> for [log in to unmask]; Mon,
13 Jan 2003 00:47:34 -0800 (PST)
which is further "proof" that the mta### machines are the ones hiccuping,
not my own computer(s)
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
