• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 384
  • Last Modified:

Exchange 07 Receive Connectors

I am using exchange to recieve our email from a host provider and then filter to the users in our network. Exchange is not running as a mail server simply routing mail from out host provider. (Running as a smart host) I have POP3 accounts setup for each user and a recieve connector within the exchange hub transport under server configuration. My problem is that we are still not getting any email. My send connector is working great and all our email is going out. I have ran the connect to internet wizard and our internet domain name is mail."ourdomainname".com, as I said before our MX record actualy points to our hosting provider (Network Solutions) and the MX name is also mail."ourdomainname".com. Not sure what else is helpful at this point. The recieve connector was set to port 25 by the wizard which seems odd I thought it should be 110 but that did not work either. Any ideas out there?
0
criceparrish
Asked:
criceparrish
  • 2
  • 2
1 Solution
 
debuggerauCommented:
I use a product called lockstep igetmail
http://www.igetmail.com/index.html

Not sure if you using Small Business Server, but that is the only product I know that allows pulling down of emails via pop without a third party tool.

Smarthost is for sending redundancy.

By having multiple MX records you can configure a secondary server, in-case the primary goes down, maybe that was your intention? Trouble is, you still need to pickup the mail from the primary..
0
 
criceparrishAuthor Commented:
The funny thing is I can get the server to send email or I can get it to receive email, but never both and I can never remember what I had as the setting for the other by the time I get the other to work. I only have one MX record. I am running SBS 08. So with igetmail do I still need to setup the pop accounts for all the users in the network pop connectors?
0
 
criceparrishAuthor Commented:
I am using Network solutions and I think the problem is on there end because igetmail will not work either. When you do the test with igetmail there is a refused to allow user error. Triple checked the username and password but still get the same thing. I think Network Solutions will just not work with exchange.
0
 
debuggerauCommented:
ok, SBS does already contain a pop3 pickup feature, so no igetmail needed.

And yes, you need to configure all accounts to get picked up.

What I need is your intentions:

Secondary mail provisioning or just a sending host with integration with Network solutions operating as a intermediary front end incoming filter?

I use this second approach, I utilize the ISP's spam filters, and from the internet, they look like they are hosting. Our Exchange is setup as a standalone email server, with igetmail (but could have used SBS), so I can send directly to the end clients and not through the ISP. This gives me some protection, while still staying intimate with the marketing dept's campaigns.

Before, we had an arrangement with the last provider, to be the secondary mail server for the domain, if our link went down, they would start to hold incoming mail for us until our were backup, and then they would push it down to us via POP.

It all depends how you have the MX's set up..

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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now