In SIMS Digest #1386, Bill Cole <[EMAIL PROTECTED]> wrote in response
to Joe Wagner:
>Stalker should probably consider addressing this as a bug, even
>thought it is very obscure and could be fixed by reworking your
>router and (if you want) MX records. If a server's one true name is
>foo.bar then it should trust that setting absolutely and never try to
>map the name to something else with the router or DNS. Assuming that
>your munging of the names is complete and accurate, it seems that
>under some circumstances SIMS will not see that its own name is
>local, and that is bad.
The only bug I see here is that SIMS actually attempts to deliver it, while
most other mail servers will simply give up with an error similar to: "Local
configuration error, mail loops back to me -- MX problem ?"
And, in fact, this _is_ a "Local configuration error" caused by the routing
table entries and MX records. Mail3 is doing exactly what it was told to do,
which is deliver mail for "domain1.com" to itself when "mail1" and "mail2"
are not reachable.
Michael A. Pasek
[EMAIL PROTECTED]
[EMAIL PROTECTED]
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
