Office 365 E1 plan - Set up send connector
Is there a way to set up a send connector in Office 365 that relays undeliverable incoming mail to another server?
Basically, I'm setting up a hybrid deployment of Office 365 - some of the emails are defined in Office 365, but SOME users are still using the legacy POP3 email provided by the web hosting provider.
The MX records are pointing at Office 365, so I need to set up Office 365 to relay mail destined for domain which is not locally deliverable to the web hosting provider's SMTP server.
In Exchange 2010/2013 I would do this by setting up an additional Send Connector, and defining the Accepted Domain to be an "Internal relay domain" instead of an "Authoritative Domain". (see here: http://technet.microsoft.com/en-us/library/bb676395(v=exchg.141).aspx)
Can you do the same thing in Office 365 somehow?
Basically, I'm setting up a hybrid deployment of Office 365 - some of the emails are defined in Office 365, but SOME users are still using the legacy POP3 email provided by the web hosting provider.
The MX records are pointing at Office 365, so I need to set up Office 365 to relay mail destined for domain which is not locally deliverable to the web hosting provider's SMTP server.
In Exchange 2010/2013 I would do this by setting up an additional Send Connector, and defining the Accepted Domain to be an "Internal relay domain" instead of an "Authoritative Domain". (see here: http://technet.microsoft.com/en-us/library/bb676395(v=exchg.141).aspx)
Can you do the same thing in Office 365 somehow?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
To answer Kimputer's question - there are two reasons why you might want to have a split setup like this.
1) Not all of your users need Office 365 and supporting them all would be expensive. In this case, the company has 3 or 4 core staff who need the features of Office 365, and then a team of 30 workers and sales people who work remotely and use email only occasionally, and they really will not benefit from anything beyond POP3. At $8 per month per user it starts getting expensive to give everyone O365.
2) Not everyone is ready to move to Office 365 all at once, it is rolled out in stages while some staff continue to use the legacy email system
1) Not all of your users need Office 365 and supporting them all would be expensive. In this case, the company has 3 or 4 core staff who need the features of Office 365, and then a team of 30 workers and sales people who work remotely and use email only occasionally, and they really will not benefit from anything beyond POP3. At $8 per month per user it starts getting expensive to give everyone O365.
2) Not everyone is ready to move to Office 365 all at once, it is rolled out in stages while some staff continue to use the legacy email system
Okay got it. My answer was wrong, because I was playing around with a P1 plan. Sorry for that.
Why use the old POP3 service when Office365 also provided POP3 support?