| Sanford Whiteman 2006-02-17, 10:41 pm |
| >This is a bit off-topic. . .
It is, since there's a better newsgroup for it, iis.smtp_nntp, and
you've also "fake" cross-posted there. If you're going to cross-post,
please really make your news client puts both newsgroups in the
header, so our clients know to cross-reply and save a ton of wasted
energy.
>When mail is addressed to someone else - it goes fine. But when the mail is
>to someone in our domain, it just sits in the SMTP server queue. I am
>guessing it is a problem with DNS somehow.
Yes, it likely is. People have problems when they point internal
machines to a DNS server publishing public IPs. Most enterprise
firewalls won't allow the "loopback NAT" necessary to get the traffic
to go out to the external i/f on the f/w, then back inside. And even
if they do, that's a ton of wasted traffic. The solution is either to
run a private IP version of your DNS zone for internal users, or use
"remote domains" in IIS SMTP (the latter being much easier) to force
mail to use an internal smarthost.
If the above does not apply, pls follow my recommendations in the
other newsgroup.
--Sandy
|