I'm only addressing the name resolution issue:
the hosts file is not an acceptable way to define names, generally. MS
has been trying to eliminate this doggie for some time now, but it
takes time.
In my case, I run DNS, with unresolved names being forwarded to my
ISP's DNS as appropriate. Then I can define certain names in the DNS
system the way I want (such as pointing a specific name that may be
defined on the Internet DNS system to point to a local non-routable
name/ip combo.)
Are you running your own DNS? If yes, define that name there. If not,
consider implementing it--DNS is easy to setup, basically start it,
and define the forwarding DNS server (your ISP's) and you are set for
the basic configuration. Then define the offending names/ips as you
wish.
[quoted text, click to view] On 10 Dec 2004 22:36:35 GMT, "Mac" <a@b.c> wrote:
>Hi,
>
>I'm having a hard time trying send mail *to some domains only* using a
>smartserver; in all (95%) other cases, the SMTP engine would send mail
>directly, as intended. Has anyone found a hidden setting for this
>scenario? or is it just impossible to do so with the vanilla SMTP
>engine of IIS?
>
>I tried to add
>
>my.isp.mailserver mx.domain.whose.mailserver.rejects.my.direct.mail
>
>to c:\WINDOWS\system32\drivers\etc\hosts, trying to trick my smtp
>service into believing that my ISP's mail server is the MX for that
>annoying domain; still, the SMTP engine retrieves the real MX (even
>though ping mx.annoyingdomain.com shows my ISP's mail server coming up,
>as intended).
>
>IIS 6.0, XP SP2 here.
>
>Thank you in advance for your suggestions,
>Mac
PeterD, the Darkstar Network
To email, fix my address!