Well, I need some help on getting mail to flow through my Exchange server. We are currently using GFI to pull POP emails to our Exchange server. This causes mail to received very slowly and I would like to have the mail flow directly through our exchange server without the use of a third party application. I have all the send and receive connectors set up, but am confused on what I need to do with the MX records; how to register them for our domain. I have two domains, but am unsure of what I need to do with them. My provider of the domains said they can make any changes I want, but that's my problem, I don't know what I need them to do.

Hi, The MX Record should point to the Public IP of HUB or EDGE in your infrastructure. Plan it accordinglyRegards from www.windowsadmin.info | www.blog.windowsadmin.info

The MX Record from our domain DNS should point to the static IP of my server? The static IP we have is assigned to our AD server, not Exchange. Do I need to update our AD server at all?

It should be pointing to ExchangeRegards from www.windowsadmin.info | www.blog.windowsadmin.info

HI, A delayed or slow delivery report could be the result of an Internet connection issue, spam filter, offline server, or any number of other causes. Have you got message tracking enabled? If not then you are going to be a little limited on what you can do. Are these internal or external messages? If external messages check the SMTP headers to see when the messages were delivered to the server. Go to the below similar issues, see if that can help you. http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/1efa521a-eed9-4e35-9ac2-c9156140155e http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/71b9a21b-6c25-4c24-8191-a4f680f431fa Apart from this, check the MX records, use http://www.mxtoolbox.com/ This test will list MX records for a domain in priority order which can be changed to less but first need to check. The MX lookup is done directly against the domain's authoritative name server, so changes to MX Records should show up instantly. And as you want without thirdparty but before making the changes just check what will be the pros and cons for that, or do you have edge servers in place/ anyother firewall etc ? Thanks

So, I need to get a separate internet connection and public static IP for my exchange server?

Hi Amit, Once the email hits my server, it's no problem for the delivery of it. The problem is that it is going to a POP email (mail.x.com) then my GFI POP2Exchange only checks the POP emails every minute. From there, the GFI has to pull them in to the server and then deliver them to the recipients. Just a lot of unneeded steps it seems. I don't have any EDGE servers, but do have a firewall in front of the servers.

Can you please share the screen shot of the error message ?

I am not getting an error message. Just wondering how to get my mail to flow directly through my exchange server versus being pulled in from webmail/POP. *Correction* I don't want to have to use a third party POP connector, i.e. GFI POP2Exchange, to retrieve my mail. I am just confused on what needs to be done to have mail flow directly through my Exchange server. I understand that having a one server topology is not recommended because it exposes the Hub Transport Server to the internet. It's being suggested that I get a Edge Transport Server and not implement it in the AD Forest, but implement it on the perimeter of the network. Currently, I have one 16MB internet connection with a static IP. The static IP points to my AD server for terminal service purposes. I see mentioned above I need the static to point to my Exchange server. By the sounds of it, I would need two internet connections and three servers. One static connection is for my AD server (static for TS) and my Hub Transport server and the other static connection for my Edge Transport server (to point the MX record to). Is this accurate?

Hi, The most common way of configuring Exchange Server to receive SMTP email is to set up an MX record for the company's domain that points to the company's public IP address. Usually, a firewall is then configured to route inbound SMTP traffic to the company's Exchange server. Configure Internet Mail Flow Directly Through a Hub Transport Server http://technet.microsoft.com/en-us/library/bb738138.aspx More useful URLs to understand and plan the things accordingly Manually Configuring Your Exchange Server for Internet Mail Delivery http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm http://technet.microsoft.com/en-us/library/aa998167(v=EXCHG.65).aspx http://technet.microsoft.com/en-us/library/aa996996(v=exchg.65).aspx http://technet.microsoft.com/en-us/library/aa998966(v=exchg.65).aspx Thanks

Hi, The most common way of configuring Exchange Server to receive SMTP email is to set up an MX record for the company's domain that points to the company's public IP address. Usually, a firewall is then configured to route inbound SMTP traffic to the company's Exchange server. Configure Internet Mail Flow Directly Through a Hub Transport Server http://technet.microsoft.com/en-us/library/bb738138.aspx More useful URLs to understand and plan the things accordingly Manually Configuring Your Exchange Server for Internet Mail Delivery http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm http://technet.microsoft.com/en-us/library/aa998167(v=EXCHG.65).aspx http://technet.microsoft.com/en-us/library/aa996996(v=exchg.65).aspx http://technet.microsoft.com/en-us/library/aa998966(v=exchg.65).aspx Thanks

Hi exchngadim, Any update for your issue, above gave some good information, if you have other conused points, please feel free let us know. Regards!Gavin TechNet Community Support

Any updates ??