Force a specific domain to be relayed (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Message Routing



Message

michauko -> Force a specific domain to be relayed (23.Jun.2008 4:33:47 AM)

Hi,

Let say my domain is "mycorp.com".
I set up a "send connector" to relay every other domain to another SMTP server (not an Exchange server). It's working fine.

I'd like to force this domain "mycorp.com" to be relayed via this SMTP.
I've tried another specific "send connector" for mycorp.com, but Exchange seems to detect "mycorp.com" is himself and then delivers e-mails locally before relaying.
This sounds logical, but I'd like to force the e-mails to be relayed in order to be checked by some other tools (anti-spam for instance) located on this other SMTP.

The e-mail will be forwarded and then come back (the other SMTP is configured to do that). That might sound stupid in terms of bandwidth and so on. But I have my reasons, trust me ;)

=> Does someone know how to force Exchange to relay even if it's local mailboxes ?

Many thanks,

Jacques M



Sembee -> RE: Force a specific domain to be relayed (24.Jun.2008 2:28:21 PM)

You are looking at this the wrong way.
The method you are trying to use will not work, because internal messages never pass through the SMTP engine to be routed by the connectors.
You need to look at the Hub Transport functionality. I haven't done it personally, but I know that Microsoft made some noise about this type of functionality being available in Exchange 2007.

Simon.



michauko -> RE: Force a specific domain to be relayed (27.Jun.2008 4:47:10 AM)

Mmm, I don't think I understand :the "send connector" is actually in "Orga. configuration" -> "Hub Transport"

I tried with a "transport rule", but I can't choose a rule like "when sent to internal user, forward to 'this' server....". Transport rules can only be used to refuse, automatically Cc or Bcc and so on...

Any idea ?

I think the "Set-TransportServer" cmdlet might help, what do you think ?


Thank you

Jacques M.



Sembee -> RE: Force a specific domain to be relayed (30.Jun.2008 1:30:44 PM)

Having queried this with others, it cannot be done in your scenario. You would create an email loop, as Exchange would simply send the email back out again.

Simon.



michauko -> RE: Force a specific domain to be relayed (2.Jul.2008 5:31:38 AM)

Yes I guess you're right.
Actually, my conf is quite more complicated (real e-mail backend on a linux server), I'm using Exchange for its calendar/address book solution (for offline work requirements).
So what I explained earlier is not totally correct. Let me explain:

I'd like my exchange server to forward everything to another SMTP, even local mailboxes. This SMTP is my real e-mail backend. There won't be any way back to the exchange server, thus no loop.

Logically, my exchange server should not send any e-mail as my user have another IMAP/SMTP account defined in outlook as the default.
The only problem is that outlook 2003 chooses randomly which server to use to send e-mails, when replying or forwarding migrated e-mails from outlook express.
If it chooses exchange, then recipients @mycorp.com are seen locally by exchange. Thus, the e-mail is delivered locally and that gives me some troubles.
That's why I want exchange to forward everything. The send connector does the trick for everything BUT @mycorp.com. So my question :)

So, do you think this would be technically possible (which setting ?) to make exchange relay everything (including so-called local mailboxes), despite the risk to make a loop ? (which I know won't occur).

Thank you

Regards,

Jacques Michau



Sembee -> RE: Force a specific domain to be relayed (2.Jul.2008 9:07:59 AM)

The short answer is what you want to do is not possible.
Exchange is an email server - if you aren't going to use it for that then I would suggest you remove it. While it will use SMTP email, that is only for traffic outside of the server. Internally SMTP is used just as a reference point. If you remove the SMTP addresses from the user accounts then you run the real risk of emails going out with invalid email addresses on them.
Furthermore Outlook is designed to be biased towards Exchange when it is connected to an Exchange server - even when other accounts are configured.

Basically you have to choose which server you want to use for email and remove the other. Then look at third party products to perhaps provide shared calendars etc. In your current scenario Exchange is not a suitable product.

Simon.



michauko -> RE: Force a specific domain to be relayed (2.Jul.2008 9:47:45 AM)

First of all, thank you for your help. The information we can find on MSExchange.org is valuable.
I'm not here to criticize Exchange, just to learn. And sometimes I learn what I call limitations - and bugs in outlook...
---
My goal is to integrate an Exchange server in a almost full-linux environment - because it's the only profesionnal way to get a good calendar solution - offline and so on - including the various opensource solution (Zimbra...) I could test.
Using 3rd-party tools to sync calendars (like Funambol) is never 100% functionnal and thus not acceptable for mobile users.

You might find the idea a bit weird, imagine 2 companies merging.

I had the possibility to move our entier infrastructure to MS, starting with our OpenLDAP - OR - try to integrate XCHG+Act. Dir the best we can.
I choosed the 2nd and it's not that complicated - but some bugs have to be corrected after that.
Finally, I could do everything I needed except the subject I submitted in this thread because of OL 2003 problems! These problems don't occur with OL 2007.
I just didn't know I wouldn't be able to tell a server to "forward everything", which is something basic.
Anyway, I'll find another solution at client's level or something.

Again, thank you
Maybe the strange problems I submitted on this forum will help some people :)



michauko -> RE: Force a specific domain to be relayed (21.Jul.2008 4:57:35 AM)

I found a solution. Not as clean as I'd like, but 100% working and scriptable.

I've created "mailcontacts" (mailbox != mailcontact) for every mailbox with an alternate e-mail address (someone@mycorp.net) as this .net domain is handled by my linux backend.
Thus, I've been able to make auto-forward for each account to these "mailcontacts". I've hidden these entries from the address book.

This way, Exchange can finally forward *every* e-mail it receives.

I just had to add these steps in my user creation procedure

1) New-MailContact -ExternalEmailAddress 'SMTP:blabla@mycorp.net' -Name 'xxx' -Alias 'xxx' -OrganizationalUnit 'bla.com/Users' -FirstName 'L' -Initials '' -LastName 'D'
2) set-mailbox -identity 'L D' -ForwardingAddress 'blabla@mycorp.net'
3) Set-MailContact -Identity 'ld' -HiddenFromAddressListsEnabled $true

Hope this will help some beginners like me



Page: [1]