Exchange 2007 / MX Records / Connection Refused

The first check is to verify port 25 has actually been forwarded through your firewall. Port 25 is used for SMTP traffic, and as you didn't mention it, I can only assume you may have omitted this part of the procedure.

Also, Exchange 2007 does not have a Receive Connector for receiving email by default. You need to create one in order to have the server receive email from the Internet: http://technet.microsoft.com/en-us/library/bb124327.aspx

-Matt

Hi Matt,

Thanks for the reply. There is no firewall, the Server has a direct, dedicated connection to the internet with a static IP. Symantec Endpoint is installed, but SMTP is listed as an allowed exception. I'll take a look at the technet article and let you know how it goes.

Craig.

Ok,

I'm using SBS2K8, the Receive Connector was set up during the installation of SBS2K8 - at least there is a Receive Connector setup up in the Exchange Management Console under Server Configuration > Hub Transport > Receive Connectors. It is called "Windows SBS Internet Receive SERVER". It is enabled and, when entering its properties page, the FQDN is set correct (mail.domain.com), 'Local IP addresses to receive mail' is set to 'all available ipv4 addresses' on port 25, 'Remote IP addresses' are set to 0.0.0.0-255.255.255.255. I am still experiencing bounced emails when sending email to user@domain.com and, when checking at network-tools.com it still says "mail.domain.com - connection refused" - any more ideas?

Cheers,

Craig.

SBS changes the scene considerably. I should have noticed you cross-posted this in the SBS zone. Did you run the appropriate wizards in the SBS Console to configure the server? That should get the inbound receive connector configured correctly.

Would you mind posting your external domain here? I can do some DNS lookups and verify everything is valid on that front.

-Matt

Hi Matt,

Yes, all wizards were run at setup. I don't mind posting the external domain as it is only being used for testing purposes anyway. It's prontoit.co.uk.

Craig.

Hi Matt,

I've since removed mx2.servage.net - it's probably not propagated yet. I can send across the network no probs to other users internally - it's just trying to get mail sent from an external internet source. I really cannot see where I've gone wrong!

Craig.

Are you able to send externally to postmaster@ (not entering domain so the spammers don't pick it up)? That address should, by default, go to the mailboxes of all designated admins on the network.

-Matt

Hi Matt,

For some reason, it just started working - I didn't change a thing then mail started coming into the Exchange mailboxes?! Now onto the next problem... Getting IMAP to work so we can access email out of the office. Again, I can't seem to see what I've done wrong lol. IMAP and POP is enabled in EMC, I've turned off all security options, just choosing basic auth but when entering mail.<domain>.co.uk into Outlook, I get an error.

Craig.

Hey Craig,

I'd suspect it may be a DNS propagation issue, but that doesn't matter, since it's working now and that's what's important.

Is there any reason why you need to use IMAP/POP? Those are pretty redundant technologies with Exchange. With an Exchange Server you'd generally make use of either OWA (through a browser) or Outlook with RPC/HTTPS for users with Outlook installed on their remote systems. With Exchange 2007, RPC/HTTPS becomes a lot easier and more attractive due to the benefits of Outlook Anywhere.

It's not uncommon to have remote users, who never visit the corporate LAN, but use RPC/HTTPS all the time to connect to their Exchange mailbox. It's much more suitable and convenient.

-Matt

Hi Matt,

Sorry about the delay in replying - Bank Hols / Easter weekend 'n all! The only reason really is so I don't have to pay for the BlackBerry exchange add on, using BIS with IMAP instead is a far cheaper option.

Cheers,

Craig.

Hi again Matt,

I've just realised that BIS has an option to monitor an OWA account, so that's that problem resolved. Thanks again for your help.

Craig.