office 365 email host, exchange smtp and FQDN issues.

Hi Folks,

quick question. I ran the exchange trouble shooting analyser as i have had a few problems after a third party upgraded some of their software which uses our outgoing SMTP.

Out setup is as follows. (not ideal and soon to be upgraded)

Our domais are hosted by BT in the uk who use office 365. We have a catch all for our domain which is connected via a pop3 connection to BT's office 365 outlook online.

I now seems to have a SMTP and FQDN that dont match ans have has a feq DNR's over the past few weeks.

Our DNS is servername.internaldomain.local

Our SMTP FQDN is webdomain.org.uk

When I lookup our MX records online the point to webdomain-org-uk.mail.eo.outlook.com

Can anyone point me in the correct direction?
dlogan83Asked:
Who is Participating?
 
Vasil Michev (MVP)Connect With a Mentor Commented:
it will, the biggest question here is why you need a catch-all in the first place? Here's a blog post by one of EE top members, explaining why using catch-all mailboxes is not a good idea: http://blog.sembee.co.uk/post/Why-you-shouldnt-use-quot3bcatch-allquot3b-mailboxes.aspx

Can you be a bit more descriptive with your intentions, so that we can better guide you?
0
 
Vasil Michev (MVP)Commented:
Catch-all mailboxes are not supported with Office 365. If your MX record points to the cloud, and the domain intent is set to authoritative, any message sent to non-existing recipient will generate an NDR.

You can instead point the MX to local email server, use it as catch-all and forward the messages to the BT account for storage.
0
 
dlogan83Author Commented:
Thanks. So would that allow me to work independently from BT? and control everything on my exchange fully.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.