
Thanks for responding. You know, I think my problems are bigger than I thought.
My internal network was set up a long time ago as CoName.Corp. When I added my Exchange server to this network domain recently, I named it Mail.CoName.Corp (FQDN).
My MX Record is pointing to mail.companyname.com. Since my MX record is pointing to this, and my server name is something different, outgong mail appears as though it is coming from a server other than what the MX record says it is. This is causing me problems. The header says Mail.CoName.Corp. It fails DNS reports (DNSStuff.com) and probably being rejected by anti-virus/spam software.
I don’t know what to do about it because the “.Corp” appendix is not a web reachable domain. It’s internal only (right?). I cannot point my MX record to an internal domain name such as “.Corp”.
So what do I do? I can’t very well change the FQDN of the Exchange server, can I?
What do you think? Thanks again!

Hi dave
I used to have the same problem. this is how I fixed it. My email goes to my firewall and is natted to my exchange box and my hosted DNS record for mail.pretend.com points towards that eternal natted address. Now for outgoing redirect the mail out a different natted ip address so the mail leaves out a different external address
You can apply a mask to change the outgoing mails severname. then add that Dns name to your hosted Dns service. So when outgoing mail is check by the recieving domains it will point back to valid dns/ip address. I use a smtp relay inbetween my firewall and exchnge box so I don’t need the outgoing mask. So basically you will have two DNS records one for incoming mail and one for outgoing mail.
Smtp.pretend.com and servername.pretend.com. Just make sure your provider gives a lower number to the income mail address.












