Re: Strange message looping

[Eugene Crosser <crosser@online.ru>]

> >      The problem is at the MX-lookup at the SMTP-client.
> >      The SMTP-client does not know which IP-addresses are
> >      owned by the system, and there is no simple reliable
> >      way to do it...  Except by listing them manually.

Thanks Matti, now I see.  Hope this will help.

> Is there any reason why the smtp TA cannot either consult localnames or
> check the interface list to automatically prevent SMTP loops?
> 
> I can see where getting a list of interface addresses could become
> disgustingly OS-centric, but consulting localnames seems harmless enough.

I understand that localnames belong to the router field, may use quite
another name, another scheme (e.g. dbm) or be absent at all, so it's not
a good idea to read this file from another program.  On the other hand,
putting almost same information in two distinct places is not a good
idea either...

> Parenthetically, I don't understand why folks put a non-primary IP address
> in their DNS as an MX RR either.  I can see doing it as a short-term fix
> for a downed machine, but, in the long term, why not just use the primary
> IP address for the system?

I don't understand it either.  They did it, not me ;-)
Probably, they did not even know the `real name' of the host;-)

Eugene