x
all questions login
General DNS & Domains Dyn Email Update Clients Dyn Developer

I have Exchange 2010 running on Windows Server 2010 with Custom DNS and Mailhop Outbound.

I have Exchange setup and configured. I can send and receive internally but I can't send or receive from/to external.

My first issue is I have no idea where to configure the mailhop outbound, and when I find where to configure it, I need to know what settings I use for mailhop outbound.

For incoming I have no idea where to start. I configured pop3 to run on port 547 and I'm able to connect to it but I can't download any messages; even ones that were sent internally.

Ideally I'd like to setup ActiveSync but that should just work but I can't figure out where that is going wrong....

Help me please :)

more ▼

asked Jan 29 at 12:59 AM

itznfb\'s gravatar image

itznfb
3 2 3 4

Old and idle question, no accepted answer selected. Closing.

Nov 23 at 09:38 AM VikingTiger ♦
10|600 characters needed characters left

2 answers:

There's an article on configuring MailHop Outbound with Exchange on the DynDNS site. While they don't list Exchange 2010, it should be similar enough to 2007 that by comparing the settings and using the Exchange 2010 documentation you can get it working.

For incoming you want to change POP3 back to the default ports. You need to configure SMTP for inbound (and outbound) email - ensure you've forwarded 25/TCP to your Exchange server. If your ISP blocks port 25/TCP then you'll want to use an alternative port - see the same MailHop documentation for more information - and MailHop Relay. Services like MXToolbox will allow you to remotely check port forwarding for SMTP.

Edit: You'll find this Microsoft article on Send Connectors useful, it covers the Exchange 2010 specifics.

more ▼

answered Jan 29 at 07:04 AM

Cry Havok\'s gravatar image

Cry Havok ♦
52.1k 13 26 222

When I run that test I get the follow results: SMTP: smtp:xxx.xxx.xxx.xxx smtp
421 4.3.2 Service not available

Not an open relay. 0 seconds - Good on Connection time 0 seconds - Good on Transaction time OK - xxx.xxx.xxx.xxx resolves to Warning - Reverse DNS does not match SMTP Banner

For the MX lookup I get these results: Pref Hostname IP Address TTL 10 http://mail.domain.com xxx.xxx.xxx.xxx 60 min

Jan 29 at 04:57 PM itznfb

There are just sooooooo many settings in Exchange that I have no idea what to enter in and nothing mentions them and there is nothing in Exchange to give me a clue as to what I need to enter. In some I don't know if I need the primary domain or mail.domain, in other I don't know if I need the mail hop out bound or my domain....

Jan 29 at 05:01 PM itznfb

It would help if you'd put all that in your Question, rather than adding comments to the answer ;)

I recommend you try Microsoft's Exchange forums for help in configuring Exchange 2010. Use the settings for older versions as a guide to what settings need changed.

Jan 29 at 05:13 PM Cry Havok ♦

I actually ran into some of these things while trying to work through the setup with the help of one of the additional documents you posted. Still no luck though. I'm setting up another virtual machine with Server 2003 and Exchange 2003 to see if I can get it working there. I'm much more familiar with Exchange 2003.

Jan 29 at 07:32 PM itznfb
10|600 characters needed characters left

As I suspected... it took about an hour to get setup and working with Exchange 2003. I'm really not sure if I want to try with 2010 again or not. My issue with 2003 so far is that Active Sync doesn't really seem to work all that well and I heard there are vast improvements in 2007 and 2010.

The Exchange 2003 are pretty accurate though. Worked first shot.

more ▼

answered Feb 01 at 09:54 PM

itznfb\'s gravatar image

itznfb
3 2 3 4

Exchange 2003 is quite simple to set up, and easy and straight-forward to administer. But in my opinion, though, it has a severe lack of configuration possibilities. The Exchange Management Console works well, and is simple to use, but on the other hand that console is pretty much all there is. Exchange 2007 offers its Exchange Power Shell, which opens a world of new possibilites. On the other hand, the integration between the command line shell and the GUI management console is straight out horrible and some administration tasks are hard to perform when you're new to Exchange 2007+

Feb 01 at 11:33 PM VikingTiger ♦
10|600 characters needed characters left
Your answer
osqa.question.ask.tags.preview.show

© 1998-2012  Dynamic Network Services Inc.  -  Legal Notices  -  Privacy Policy  -  Contacts     

Powered by AnswerHub - Enterprise Social Q&A