On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
This means
that they have multiple MX records for a domain that indicates multiple
servers that are capable of handling mail. If I don't rely on the MX
records when resolving the address, but rather pick a one or more
corporate mail servers to connect to from my SMTP server (configured as
a gateway), then I have to manually ensure that I keep my mail server
addresses synchronized with the MX configuration.
Am I making sense here? Am I crazy? I'm starting to feel crazy...
You are making perfect sense.
The way you *should* handle this is by having round robin DNS on A or
CNAME records for the mail gateway. Because, as has already been
discussed, it is a host which you have chosen and not a mail domain
you're seeking to resolve.
However I can see benefits for providing an alternative option whereby
you could specify a mail domain to forward all mail to instead of a
host.
They are significantly different at a logical/functional level, but
IMO there is no reason why we shouldn't allow both just as long as we
can clearly differentiate between gateway host and gateway domain,
because their behaviour will not be the same in exception & alternate
use-cases.
If you want to raise an enhancement in JIRA and attach your patch I'll
look at it.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
