On Thu, Sep 06, 2001 at 01:39:48PM -0400, Wietse Venema wrote:
> Andrey Savochkin:
> > > That is not practical. Surely there is an API to find out if an IP
> > > address connects to the machine itself. If every UNIX system on
> > > this planet can do it, then surely Linux can do it.
> >
> > Let me correct you: you need to recognize not addresses that result in
> > connecting to the _machine_ itself, but connecting to the same _MTA_.
>
> The SMTP RFC requires that user@[ip.address] is correctly recognized
> as a final destination. This requires that Linux provides the MTA
> with information about IP addresses that correspond with INADDR_ANY.
I see no such thing in the RFC. What I do see is that you're
allow to use the [IP address] notation. It can't see where it
says that if that IP address is an IP address of the local host,
that it should accept it as the final destination.
I can perfectly imagine that the same hosts runs serveral MTAs,
on different IP addresses, and that both might have the same
username, but it's for a different person.
If an MTA doesn't listen to INADDR_ANY, why should it need to
know all addresses that might correspond to it? That shouldn't
mean that if it does listen to INADDR_ANY, it should know them
all, but that could be something an MTA might want to do.
Like Andrey says, it needs to go to the same MTA.
If for some reason it was needed to use the IP address in the
destination, it's very likely that when it reaches the final
host, it will be a connection to that IP address. Atleast, seen
from the connecting host. If it's using NAT, maybe there should
be some option to tell it to accept that IP address as a final
destination too.
Kurt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 07 2001 - 21:00:41 EST