Delayed/unable to send to AOL addresses with new Exchange 2003 server

Posted on 2006-04-09
Last Modified: 2008-02-01
Our domain at work was a single Windows 2003 server (fileserver.domain.local)  Then I added an Exchange 2003 server as a member server and simply added it to the domain (exchange.domain.local).  I then ran the SMTP wizard which appears to have amended the recipients policy by adding as a suffix so that when I add a new user it automatically creates 3 email addresses for them (user@domain.local - & an X400 one).

Everything seemed to be working fine, users were able to send and recieve internal and external emails however I noticed that emails sent to AOL were getting delayed and then were unable to be delivered so I ran my mailserver IP through dnsstuff and it appeared that I didn't have a PTR record.  I contacted my ISP who set this up for me however they were unable to set the record to point to exchange.domain.local, they had to set it to (which obviously isn't the name of my mailserver)

AOL emails still aren't going so I wondered if anyone could advise on what to do next?  Can I simply change my server name to or will that break anything?
Question by:philz75
    LVL 18

    Expert Comment

    next step is to edit what your exchange server tells the world when a SMTP connection is made.
    go to ESM -> servername -> protocols -> SMTP -> right click default virtual server, properties
    go to delivery -> advanced ->
    change the Fully qualified domain name to what you have the PTR record set to.  Restart SMTP

    from the server do
    telnet localhost 25
    what do you see?

    Also verify that the ISP setup the PTR,   go to an outside connection with a DNS not provided by that ISP, and do:
    xxx = the IP address of your outside mail server connection
    should resolve to proper
    LVL 104

    Expert Comment

    Unless you are very lucky, if you are on a DSL or cable connection then you can make all the changes you like, AOL will never accept your email. It doesn't matter if you have a dynamic or static IP, they simply will not accept your email.

    You will need to use an SMTP Connector to route email through the ISPs SMTP Server.

    It can help to make the changes that Carl has outlined above, although you don't need to restart the SMTP service to get the name announcement to take affect - it is live.

    You can also try putting your external domain name in to and see what it says.


    Author Comment


    I'd already done the FQDN bit so here's the result of the telnet and nslookup (telnet seems to be ok but nslookup is still not working)

    220 Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at  Sun, 9 Apr 2006 23:08:01 +0100

    C:\Documents and Settings\Admin>nslookup 81.*.*.19
    Address:  62.*.*.39

    *** can't find 81.*.*.19: Non-existent domain

    Does this mean that my ISP hasn't done my PTR yet?
    LVL 18

    Accepted Solution

    Either the ISP is lazy, doesn't know how to comply with your request, or because of the nature of DNS there can be a substantial delay of up to 48 hours.
    LVL 104

    Expert Comment

    The easiest way to find out is to simply put the domain in to and see whether that reports a reverse lookup or not.


    Author Comment

    Carl, you were right, the ISP was either lazy or there was a propagation problem as I've just checked today and everything is ok now.

    Cheers for your help

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
    Use email signature images to promote corporate certifications and industry awards.
    In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
    The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    23 Experts available now in Live!

    Get 1:1 Help Now