Aaron Schrab wrote:
be a way. I currently grab the IP address from the first
Received: header inserted by my ISP
Now, for a real challenge. My ISP (Interlog) owns both the
interlog.com and interlog.net domains. Sometimes incoming email
goes through 2 machines...
================================================================
Received: from mx2.mail.interlog.net
(root(_at_)mx2(_dot_)mail(_dot_)interlog(_dot_)net
[198.53.145.12]
by gold.interlog.com (8.8.5/8.8.5) with ESMTP id TAA19950;
Sat, 11 Oct 1997 19:50:52 -0400 (EDT)
From: 111097t7C10(_at_)tmi-osm(_dot_)net
Received: from webcube.cscent.net ([206.85.231.10])
by mx2.mail.interlog.net (8.8.5/8.8.5) with ESMTP id
TAA26734;
Sat, 11 Oct 1997 19:46:53 -0400 (EDT)
================================================================
...and sometimes it goes through only one Interlog machine...
================================================================
Received: from kudonet.com (kudonet.com [165.227.52.1])
by gold.interlog.com (8.8.5/8.8.5) with SMTP id UAA13144
for <waltdnes(_at_)interlog(_dot_)com>; Sun, 12 Oct 1997 20:08:41
-0400 (EDT)
From: nao(_at_)crawford(_dot_)com
================================================================
How would you trap that? Would a reply to an address like
postmaster(_at_)165(_dot_)227(_dot_)52(_dot_)1 work? That would save the
overhead of
spawning NSLOOKUP.
--
Walter Dnes (Toronto)
<waltdnes(_at_)interlog(_dot_)com>