Jump to content

Recommended Posts

Posted

I'm in the process of configuring an exchange server and I've encountered a problem where it's not accepting emails from external domains.

 

I can email internally and I can email outbound from the OWA, however if I try to email from (say) Gmail, it doesn't appear.

It doesn't, however, give me a bounceback error at Gmail.

 

 

I think I've configured the MX/A records correctly for DNS and my ISP confirmed they can telnet using the appropriate information.

 

Any ideas?

Posted

Have you got 'Accepted Domains' setup? (I suspect internal mails ignore the domain part)

 

And (though I'm less familiar with this) have you got send/receive connectors setup?

 

What's your mail domain? (PM me if you prefer)

Posted
Have you got 'Accepted Domains' setup? (I suspect internal mails ignore the domain part)

 

And (though I'm less familiar with this) have you got send/receive connectors setup?

 

What's your mail domain? (PM me if you prefer)

 

I got it sorted fortunately!

Turns out it was because I had an alternate DNS server in the IP Settings which was no longer in use.

Strange one...!

 

Then after many hours of getting my head around auto discover and SAN CERTS it works!

Strangely however, it doesn't work on mobile if I'm connected to the wifi where the exchange server is.

I'll check again next week, but I expect it's more DNS/A record problems.

 

First time doing this, if anyone else is following and has any problems, give me a shout.

I may have encountered them myself in the past few days!

Posted

Jolly good.

 

I did reply yesterday on my phone, but the app is misbehaving more than it's behaving at the moment so it refused to post.

 

Is your wifi segregated/VLAN'd? We have a local DNS entry for mail.ourdomain.com so we then have to put a zone bridge on the Smoothwall to allow traffic from the wifi to the Exchange server; this means the mobiles are making use of the same SSL cert for the same url (mail.ourdomain.com) instead of using the local servername and throwing SSL errors.

 

Peter

Posted

Not too sure about that, something I'll have to look at when I'm back in on Tuesday.

 

Meanwhile, for some reason I'm now being prevented from sending emails...

I was able to, and now can't!

 

In the Queue view, I'm receiving a 'LED=441 4.4.1. Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10060, Win32 error code: 10060." Attempted failover to alternate host, but that did not succeed'

 

Strangely, I cannot PING Google.com but I CAN browse to it?

Any clues?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...