Domain example.com has all mail delivered to a linux box, doing a nice job of spam filtering. This is using IMAP for mail collection by clients…
I’ve got a Windows Small Business Server, sbs.example.com, some uses want to use the exchange mailbox - all users want to use the sharepoint site.
So email is all arriving on my linux box, and if the user wants exchange I’m forwarding the mail to user@sbs.example.com, this part all works fine. Users on the exchange box can send email and the primary address space is set to example.com
My problem is that the exchange server insists on sending mail to example.com itself, not touching the external smtp settings regardless of whether I set it to not be the authoritive mail machine.
So to clarify, it user1@example.com who is an exhange user mails to anything userX@example.com it is not going through the external smtp connector that I’ve specified.
Exchange will always try and deliver the email locally first. If the domain is managed by that server and it doesn’t find the address on the server it will toss it.
What you need is the *@domain.com option which delivers all email not found on the local server to a remote host. Why would people want the linux box anyway? Why not enable IMAP on the exchange box?
I think your best option would be to create a sub domain like @boo.example.com for exchange and the main domain on linux and then forward the main domain to boo.example.com. Then set the reply to address as the @example.com on exchange or you can set the exchange server to send through the Linux box as a relay and do header re-writing.
Basically you would have to use a different domain on the exchange server as far as I know.
Your description is exactly what I tried, but exchange recognises it, so I think my only option is to use example.com (primary domain) on the linux server, and then cheat and use qwerty.com on the exchange server with the send address as example.com (which I’ve done and it works).
Just need to get sign off to do it this way. The tickbox in policies that is titled “This Exchange Organization is responsible for all mail delivery to this address” doesn’t seem to work. According to MSDN this should mean that it will never try to do local delivery, but it does :sigh:
