S�ren Hilmer wrote:
> Noel J. Bergman wrote:
> > In my view, it should be done by our DNS lookup code. See RFC 2821,
> > section 5:
> >
> > The destination host (perhaps taken from the preferred MX record) may
> > be multihomed, in which case the domain name resolver will return a
> > list of alternative IP addresses. It is the responsibility of the
> > domain name resolver interface to have ordered this list by
> > decreasing preference if necessary, and SMTP MUST try them in the
> > order presented.
> >
> > So it is handling a multihomed destination that needs to be addressed.
> the problem of handling it at the DNS lookup level (which I
> agree is the conceptually right thing to do) is that the
> logging from RemoteDelivery gets more cryptic as the link
> to the MX record is lost
The return is a Collection of String objects. Each one is currently of the
form "host", but if we were to handle multi-homed hosts by using "host/IP",
it seems to me that we could either parse it directly, or change the way we
construct the URLName.
Thoughts?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
