We have full Exchange 2007 Server Standard running on 64 bit Windows Server 2003. We want to keep our current SMTP/POP3 server to handle most domains and for it's ease of use. We're testing with the duplication of a few accounts to Exchange - forwarding copies of messages and using the legacy mail server to send mails. We need Exchange for group features, more advanced web client and Blackberry BES use.
We already have a firewall, spam firewall (appliance) and legacy SMTP/POP server - we don't want to ad an Edge Transport. We want to use only Hub Transport.
Exchange uses our legacy server to send outgoing messages without any problem.
The OWA works wonderfully.
I created an Internet based Receive connector in the Hub Transport, and I think it's as wide open as I can make it.
I tried "set-transporteconfig -InternalSMTPServers 192.168.x.x" in the management shell.
The legacy computer FQDN is: mail.domain.com (domain.com is used in place of actual)
The exchange computer FQDN is: exchange.domain.com
I forward the messages from mail.domain.com by sending to firstname.lastname@example.org
Generating server: domain.com
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##
I expect the rejection is caused because technically the user only exists as email@example.com, not firstname.lastname@example.org? I would attempt to use the address rewrite function, but it appears that it only works in Edge Transport. Is there a different way I can send the message, or a way to force the subdomain to be accepted (I did add it to "Accepted Domains", but that didn't help).
I really want to resolve this so I can move on to the next set of problems I'm sure is waiting around the corner.