Search results for query: *

I also had to add a reverse lookup for the exchange server to my DNS to resolve one or two problem domains. I appears that they do a reverse lookup before accepting any e-mails.

I think I may have it solved :) After spending two hours on the phone with MS it came down to a trailing period on my DNS name. Apparently some recipients are perticular about correct DNS suffixes. Make sure that you have a correct and valid name setting as your DNS suffix on your exchange...

I have quite a number of domains that would have to be routed that way. I sure hope there is a permanent solution to this somewhere or else I'll end up managing a seperate routing table within Exchange :(

I can reach clients via telnet on port 25 and Transfer Mode is set to Inbound & Outbound. I am using an external DNS server and the Exchantge server is behind a firewall but all relevant ports are open. My problem is that this only affects a small number of e-mails per day. I can see no...

No. No double dot names. Our default reply address has firstname.lastname@company.com but none of the recipients do.

Nope. Still the same issue. I tried pointing Exchange to a different DNS server but got the same result. All the clients have MX records listed so I'm stumped. I double checked all the settings I could think of.

Hi Folks, I'm running exchange 5.5 SP4 on a Windows 2000 box. I have a number of outbound messages stuck in my queue awaiting delivery with <Host Unreachable> as the error message. I can reach the hosts mail server (using nslookup and ping) but the messages are not delivered. I can reach the...