From: Ray Olszewski <ray@comarre.com>
To: Peter <heisspf@skyinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Reverse DNS
Date: Mon, 16 May 2005 22:01:48 -0700 [thread overview]
Message-ID: <42897ABC.4030506@comarre.com> (raw)
In-Reply-To: <200505170217.j4H2HKo6000609@skyinet.net>
I added the mailing list back in with this reply.
Peter wrote:
> ray@comarre.com said:
>
>>3. But perhaps the problem is that you are not actually sending your mail
>>from the above IP address? Looking at the headers for the message you sent
>>here, it came from an MTA at 203.87.189.146 . Let's look at that address ...
>
>
>> ray@kuryakin:~$ host 203.87.189.146
>> 203.87.189.146 does not exist, try again
>
>
>>So there is the problem; the *actual* IP address of your broadband
>>connection lacks a reverse-DNS entry.
>
>
> Yes I send the mail via the broadband ISP. Now, cat /etc/resolv.conf I get:
>
> nameserver 203.87.128.3
> search meridiantelekoms.com
>
> then I get:
>
> heisspf@~:$ host 203.87.128.3
> 3.128.87.203.in-addr.arpa domain name pointer dns1.meridiantelekoms.com.
>
> heisspf@~:$ host dns1.meridiantelekoms.com
> dns1.meridiantelekoms.com has address 203.87.128.3
>
> So there is a reverse DNS.
Foe the nameserver there is, but that is irrelevent to your problem.
>
> Where does that "actual" ISP 203.87.189.146 in my mail then come from?
>
Every e-mail has, in addition to the headers you see (like To: and
From:), a bunch of other headers that most MUAs do not display. In
particular, there will be a series of Received: headers that report the
path of SMTP relays that the message took to get from the sender to the
recipient. All MUAs I've used offer the option of displaying these
headers, but there is really no standard for how to do that, so I cannot
tell you how your MUA (whatever it is) can be set to show them.
In the case of the message you sent to me, it contained this final
Received: header --
Received: from [203.87.189.146] (helo=skyinet.net) by celine.comarre.com
with esmtp (Exim 3.35 #1 (Debian)) id 1DXrdx-0004FF-00 for
<ray@comarre.com>; Mon, 16 May 20
This tells me that your MTA runs on a machine that appears to the
Internet to have the IP address 203.87.189.146 ... whether it itself has
that address or is behind a router that SNATs it to that address is
something I cannot determine. But for the AOL purposes, it does not
matter. What matters is that when you send a messge to someone@aol.com,
the AOL MTA sees the message as coming from an MTA at 203.87.189.146 and
tries to reverse-lookup that address ... which, as I indicated before, I
cannot do, so AOL probably cannot do it either.
> ray@comarre.com said:
>
>>This lookup failure suggests a degree of sloppiness at your ISP that would
>>have me looking elsewhere for a service provider.
>
>
> Meridiantelekoms has set-up and operates the broadband connection, therefore,
> I can't possibly change them. In the meantime I have informed them of the
> problem.
At least here in the USA, most communities have more than one broadband
supplier. Were I to face your problem, I would at least consider
changing who I got my broadband service from ... especially if requests
to fix the problem were ignored.
> ray@comarre.com said:
>
>>In the meantime -- does your ISP provide a mail forwarder? Most do. If so,
>>setting up your MTA to send mail through that forwarder would probably
>>satisfy AOL's requirements.
>
>
> As I said skyinet.net my former ISP delivered mail to AOL properly via the
> modem connection. Now I am still sending and receiving mail using skyinet
> through meridaintelekoms. Therefore I conclude meridian acts as a mail
> forwarder. Would that need a special setting-up?
>
> Thanks & regards
A mail forwarder is an MTA that your MTA uses to send all messages. That
is, you set it up to send all outgoing mail to (for example)
mail.myisp.com . For this to work, mail.myisp.com needs to know that it
is supposed to forward (relay) messages for you, and the details of how,
even whether, you can use it that way are entirely under the control of
your ISP.
I do recall your mentioning previously (some months back) that you were
somehow using skyinet through your broadband connection, but if you ever
told us the details, I've forgotten them. Do note that if the message
you sent to me is an example of what you are referring to, it doesn't
really use skyinet to send the mail ... your on-LAN MTA is sending the
mail directing to the destination MTA, but is just displaying
<heisspf@skyinet.net> as the From: address. That approach won't solve
your AOL problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next parent reply other threads:[~2005-05-17 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505170217.j4H2HKo6000609@skyinet.net>
2005-05-17 5:01 ` Ray Olszewski [this message]
2005-05-24 8:05 ` Reverse DNS Peter
2005-05-16 7:23 Peter H.
2005-05-16 15:14 ` Ray Olszewski
2005-05-17 8:30 ` Nathan Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42897ABC.4030506@comarre.com \
--to=ray@comarre.com \
--cc=heisspf@skyinet.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox