Problem solved (Re:root 's mail) 2003-07-31 - By Jason Dale
Back
Hi All,
I just wanted to thank you all for your input,
and to let you know how I solved the problem.
Naturally there are other (and better) ways to
do things, but these are the steps I took:
For issues concerning sendmail, I would
recommend that you go to www.sendmail.org ,
and search the FAQ for the errors that you may get
on or from a sendmail server.
1) I enabled the exim server on my test firewall machine
to accept domain literals. I run a very old exim version
because this machine is redundant in it's function and does
not require updates.
Exim version 3.13-1
a) Edit file /etc/exim/config
b) Uncomment the line with 'local_domains_include_host_literals' OR
supply the literals in your local_domains file.
c) Comment out the line containing 'forbid_domain_literals'
d) Restart the exim daemon 'service exim restart' or
'/etc/rc.d/init.d/exim restart'
2) Because the test firewall now accepts domain literals, it will accept
the
mail messages, because the attached IP address in the mail has been
cleared in the relay rules on the test firewall machine.
The next step is to perform a similar action on the RH server with the
IP 1.2.3.4, which sits behind the test firewall.
a) Enable domain literals: ensure that you have
FEATURE(`accept_unresolvable_domains') in your sendmail.mc file.
If you need to make any changes to the sendmail.mc file, run the
command
m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf
b) Add the line [1.2.3.4] in your local-host-names file (Including the
brackets). You will now be able to sendmail to root@[1.2.3.4] or
postmaster@[1.2.3.4]. Postmaster by default is aliases to root
in the /etc/aliases file.
lastly, I restarted the sendmail daemon.
service sendmail restart
Regards, Jason
-- -- Original Message -- --
From: "James P. Roberts" <punster@(protected)>
To: <seawolf-list@(protected)>
Sent: Tuesday, July 29, 2003 8:23 PM
Subject: Re:root's mail
> > =>> Does anyone know how to send mail to an IP address rather
> > =>> than a domain name, for example, sending mail to
> > =>>
> > =>> root@(protected)
> > =>>
> > =>> I have put the IP address 1.2.3.4 in the 'local-host-names' file
> > =>> and restarted sendmail. Even that did not work. I get
> > =>> "Unrouteable mail domain 1.2.3.4" error messages.
> > =>>
> > =>> Any ideas?
> > =>>
> > =>> Thanks, Jason
> >
> > Just send it to root@[1.2.3.4]
>
> That is correct, I believe. The email RFC (I forget which one, and too
busy
> to look it up) says that when specifying an IP instead of a domain name,
one
> must put it in square brackets, as the previous contributor points out.
This
> is to distinguish the IP 1.2.3.4 from the domain name "1.2.3.4" (to
clarify a
> bit, just imagine a domain called "1.2.3.org")
>
> I think Sendmail was trying to look up the MX record of a domain named
> "1.2.3.4" (and failing, of course). That is the source of your error
message.
> When you put it in brackets, Sendmail should (theoretically) know it's an
IP,
> not a hostname, and therefore won't try to look up the MX record (I
think).
>
> By the way, an MX record returns a hostname, not an IP. After retrieving
the
> MX hostname, the corresponding IP address of that MX host is looked up in
the
> DNS. In the case of an IP being erroneously entered in an MX record, it
will
> trigger problems very like the one you already encountered, in which
mailers
> will insist the "domain is unrouteable."
>
> Now, how to tell Sendmail that it should accept mail for [1.2.3.4] as
local...
> that's another story, and I do not know enough about Sendmail to advise
you.
> Perhaps it will work by default for the IP of the host that Sendmail is
> running on. Does anyone know?
>
> Jim
>
>
> __ ____ ____ ____ ____ ____ ____ ____ ____ ____
> Seawolf-list mailing list
> Seawolf-list@(protected)
> https://www.redhat.com/mailman/listinfo/seawolf-list
|
|
