Depends on your firewall, 'ne? :-)
If you are sending to archive.fope.microsoft.com (or whatever host), can you open port 25 FROM THE HT SERVERS? I'm guessing the answer is "no". Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Bill Egan [mailto:william.e...@gmail.com] Sent: Tuesday, September 07, 2010 5:42 PM To: MS-Exchange Admin Issues Subject: Re: Specific connectors for specific address spaces Let me try to clarify (but I may only muddy the waters...) We have a Send Connector that gets all outbound mail from our HT boxes to our ET boxes (source servers are the HTs address space is * and the smarthost target is the ET) and another send connector that moves it from the ET to the internet (source is ETs and smarthost target is mail.messaging.microsoft.com (we use EHS/FOPE for outbound as well.) If we take away the HT-->ET send connector, mail flow breaks. So the first question is *should* we have to have a Send Connector to move the mail from HT internal to the ET in DMZ segment, or should it move automagically since its all between exchange servers? If we DO need this HT-->ET send connector, then we would need to create the specific connectors the same way every time, I would think. 1 to get @example.com from HT-->ET and another to get @example.com from ET to wherever (maybe a specific smarthost.) If one should not need the send connector to get the mail from HT to ET, what are we doing wrong? (that we've been doing wrong for years...) thanks, bill On Tue, Sep 7, 2010 at 5:13 PM, Michael B. Smith <mich...@smithcons.com> wrote: > Depends on your firewall, 'ne? > > Regards, > > Michael B. Smith > Consultant and Exchange MVP > http://TheEssentialExchange.com > > > -----Original Message----- > From: Russ Patterson [mailto:rus...@gmail.com] > Sent: Tuesday, September 07, 2010 4:48 PM > To: MS-Exchange Admin Issues > Subject: Specific connectors for specific address spaces > > Hello everyone - > > We're testing Exchange hosted services for archive via FOPE. Their > documentation strongly recommends using a dedicated smtp connector for > their archive address space to get the Journal mailbox traffic to > them. I set up a send connector pointing at the given archive > namespace, and set my Edge server as the source server. (This is all > Exchange 2007.) > > Mail queued up on my hubs - with a next hop destination of my new connector, > untill we created a connector from my hubs to the edge _with the same > specific archive address space_. > > I expected the old & well used * address space conn to get the journal email > to my Edge, and then the specific address space to shoot straight at the > Microsoft Archive name space - but it didn't, apparently. My question is - if > you're going to set up a specific connector for a specific external address > space, do you have to create it all the way thru your org? i.e. like we did - > one conn from Hub to Edge with the specific address space, and then the one > from Edge to that spacific address space on the outside? > > Thanks all! > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
