The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Not able send email to any of AOL users

Discussion in 'E-mail Discussions' started by crazyaboutlinux, Mar 6, 2009.

  1. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    hi

    we are not able send email to any of AOL users below are the last email log from the server .

    if anyone know how to resolve this please update on this...
    ----------------------------------------------
    2009-03-06 20:08:32 1LfbC3-0000sC-Uu <= test@fusiontechindia.com H=localhost (fusiontechindia.com) [127.0.0.1] P=esmtpa A=fixed_login:test@fusiontechindia.com S=877 id=1139.61.17.209.216.1236350311.squirrel@fusiontechindia.com T="test mail at 8:08"
    2009-03-06 20:08:42 1LfbC3-0000sC-Uu ** jalaraminfotech@aol.com R=fail_remote_domains: The mail server could not deliver mail to jalaraminfotech@aol.com. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries.
    2009-03-06 20:08:42 1LfbC3-0000sC-Uu Completed
    ----------------------------------------------

    Thanks & Regards,
    Nilesh
     
  2. Pixelpirat

    Pixelpirat Well-Known Member

    Joined:
    Jun 6, 2006
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Germany
    hi,

    AOL says:
    host -t mx fusiontechindia.com
    fusiontechindia.com mail is handled by 0 fusiontechindia.com.

    Where is your mx record?
    IMHO you can't deliver mails to AOL without mx record


    HTH
    Pixelpirat
     
  3. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    here is MX record details

    [root@saturn ~]# dig -t MX fusiontechindia.com

    ; <<>> DiG 9.2.4 <<>> -t MX fusiontechindia.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41581
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;fusiontechindia.com. IN MX

    ;; ANSWER SECTION:
    fusiontechindia.com. 14400 IN MX 0 fusiontechindia.com.

    ;; AUTHORITY SECTION:
    fusiontechindia.com. 86400 IN NS ns10.jinfo.net.
    fusiontechindia.com. 86400 IN NS ns9.jinfo.net.

    ;; ADDITIONAL SECTION:
    fusiontechindia.com. 14400 IN A 69.72.212.42

    ;; Query time: 0 msec
    ;; SERVER: 69.72.212.42#53(69.72.212.42)
    ;; WHEN: Sat Mar 7 11:13:07 2009
    ;; MSG SIZE rcvd: 115

    [root@saturn ~]#
     
  4. Pixelpirat

    Pixelpirat Well-Known Member

    Joined:
    Jun 6, 2006
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Germany
  5. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    we have pointed this domain to 69.72.212.42 server & mail.fusiontechindia.com is pointing on the same

    for your information earlier we got Retry Time Out Error now its coming this

    DNS records
    name class type data time to live
    fusiontechindia.com IN TXT v=spf1 a mx ip4:69.72.212.42 ?all 14400s (04:00:00)
    fusiontechindia.com IN MX
    preference: 0
    exchange: fusiontechindia.com
    14400s (04:00:00)
    fusiontechindia.com IN SOA
    server: ns9.jinfo.net
    email: saturn.inetindia.net
    serial: 2009013103
    refresh: 86400
    retry: 7200
    expire: 3600000
    minimum ttl: 86400
    86400s (1.00:00:00)
    fusiontechindia.com IN NS ns9.jinfo.net 86400s (1.00:00:00)
    fusiontechindia.com IN NS ns10.jinfo.net 86400s (1.00:00:00)
    fusiontechindia.com IN A 69.72.212.42 14400s (04:00:00)
    42.212.72.69.in-addr.arpa IN PTR saturn.inetindia.net 11421s (03:10:21)
     
  6. Pixelpirat

    Pixelpirat Well-Known Member

    Joined:
    Jun 6, 2006
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Germany
    Your mx isn't pointing to mail.fusiontechindia.com, he is pointing to fusiontechindia.com

    If you changed it and it doesn't work again, then contact the postmaster of aol.
    its possible that aol blocked your ip.
     
  7. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,383
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Are you able to send out any e-mail from your server?

    Do a:

    Code:
    dig aol.com MX
    from the server that you are trying to send from.

    It looks like your server is not able to resolve aol.com or find any MX records for it. This may point to a problem with your DNS resolvers on your server.
     
  8. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    No, im not able to send out any email from our sever & not able to receive emails from AOL server

    im getting below msg from our server check this

    [root@saturn ~]# telnet mailin-01.mx.aol.com 25
    mailin-01.mx.aol.com/25: Name or service not known


    what do i do of this ??

    Do a:

    Code:
    dig aol.com MX
    Regards,
    Nilesh
     
    #8 crazyaboutlinux, Mar 7, 2009
    Last edited: Mar 7, 2009
  9. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,383
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    You need to do this on the shell on the server in question.

    Is this a managed server or unmanaged server?
     
  10. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    [root@saturn ~]# dig aol.com MX

    ; <<>> DiG 9.2.4 <<>> aol.com MX
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38059
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;aol.com. IN MX

    ;; AUTHORITY SECTION:
    aol.com. 16369 IN NS dns-01.ns.aol.com.
    aol.com. 16369 IN NS dns-02.ns.aol.com.
    aol.com. 16369 IN NS dns-06.ns.aol.com.
    aol.com. 16369 IN NS dns-07.ns.aol.com.

    ;; Query time: 0 msec
    ;; SERVER: 69.72.212.43#53(69.72.212.43)
    ;; WHEN: Sat Mar 7 20:12:48 2009
    ;; MSG SIZE rcvd: 112

    [root@saturn ~]#


    this is a managed server
     
  11. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,383
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Talk to the datacenter about this. It looks like you don't have the correct DNS resolvers in your resolver set up.

    You are not getting any answers to your aol.com MX record query from dig. This means that your server is not able to look up the aol.com DNS record and see where to send the messages to.

    Your datacenter should be able to help you with this. They should have DNS resolvers for your server to use and they should be able to set these up for you.
     
  12. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    can i check this at my end

    i have complete shell & root access

    Regards,
    Nilesh
     
  13. nilesh_kolte

    nilesh_kolte Well-Known Member

    Joined:
    Apr 13, 2006
    Messages:
    65
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Pune ,India
    cPanel Access Level:
    Root Administrator
    Hello,

    Seems that your domain don't have reverse DNS record.Add the RDNS for the domain also try to get the MX for aol.com from your server.



    Regards,
     
  14. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    hello,

    thanks for your opinion but RDNS is already set you can check below for the same

    DNS records
    name class type data time to live
    fusiontechindia.com IN TXT v=spf1 a mx ip4:69.72.212.42 ?all 14400s (04:00:00)
    fusiontechindia.com IN MX
    preference: 0
    exchange: fusiontechindia.com
    14400s (04:00:00)
    fusiontechindia.com IN SOA
    server: ns9.jinfo.net
    email: saturn.inetindia.net
    serial: 2009013103
    refresh: 86400
    retry: 7200
    expire: 3600000
    minimum ttl: 86400
    86400s (1.00:00:00)
    fusiontechindia.com IN NS ns10.jinfo.net 86400s (1.00:00:00)
    fusiontechindia.com IN NS ns9.jinfo.net 86400s (1.00:00:00)
    fusiontechindia.com IN A 69.72.212.42 14400s (04:00:00)
    42.212.72.69.in-addr.arpa IN PTR saturn.inetindia.net 12086s (03:21:26)

    -- end --
     
  15. mtindor

    mtindor Well-Known Member

    Joined:
    Sep 14, 2004
    Messages:
    1,281
    Likes Received:
    37
    Trophy Points:
    48
    Location:
    inside a catfish
    cPanel Access Level:
    Root Administrator
    As somebody has already pointed out, your resolvers don't know how to find AOL.COM.

    Your resolvers are listed in /etc/resolv.conf

    If the nameservers in /etc/resolv.conf are the nameservers that your provider gave to you to use, contact them and tell them that their resolvers are broken.

    dig aol.com mx @resolver.qwest.net
    - if your resolvers are working they should show similar to this

    Mike
     
  16. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    yes, it is showing the same please check below details


    [root@saturn ~]# dig aol.com mx @resolver.qwest.net

    ; <<>> DiG 9.2.4 <<>> aol.com mx @resolver.qwest.net
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9031
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 17

    ;; QUESTION SECTION:
    ;aol.com. IN MX

    ;; ANSWER SECTION:
    aol.com. 1334 IN MX 15 mailin-03.mx.aol.com.
    aol.com. 1334 IN MX 15 mailin-04.mx.aol.com.
    aol.com. 1334 IN MX 15 mailin-01.mx.aol.com.
    aol.com. 1334 IN MX 15 mailin-02.mx.aol.com.

    ;; AUTHORITY SECTION:
    aol.com. 1334 IN NS dns-02.ns.aol.com.
    aol.com. 1334 IN NS dns-07.ns.aol.com.
    aol.com. 1334 IN NS dns-01.ns.aol.com.
    aol.com. 1334 IN NS dns-06.ns.aol.com.

    ;; ADDITIONAL SECTION:
    mailin-02.mx.aol.com. 2733 IN A 205.188.155.72
    mailin-02.mx.aol.com. 2733 IN A 205.188.249.91
    mailin-02.mx.aol.com. 2733 IN A 64.12.137.89
    mailin-02.mx.aol.com. 2733 IN A 64.12.138.120
    mailin-03.mx.aol.com. 183 IN A 205.188.109.56
    mailin-03.mx.aol.com. 183 IN A 205.188.252.17
    mailin-03.mx.aol.com. 183 IN A 64.12.138.153
    mailin-04.mx.aol.com. 185 IN A 64.12.138.57
    mailin-04.mx.aol.com. 185 IN A 64.12.138.88
    mailin-04.mx.aol.com. 185 IN A 205.188.159.216
    mailin-01.mx.aol.com. 34 IN A 64.12.139.249
    mailin-01.mx.aol.com. 34 IN A 205.188.156.248
    mailin-01.mx.aol.com. 34 IN A 205.188.159.57
    dns-07.ns.aol.com. 297 IN A 64.236.1.107
    dns-06.ns.aol.com. 3269 IN A 149.174.54.153
    dns-02.ns.aol.com. 3360 IN A 205.188.157.232
    dns-01.ns.aol.com. 41680 IN A 64.12.51.132

    ;; Query time: 9 msec
    ;; SERVER: 205.171.3.65#53(205.171.3.65)
    ;; WHEN: Mon Mar 9 20:01:29 2009
    ;; MSG SIZE rcvd: 491
     
  17. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,383
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    What is the contents of the /etc/resolv.conf file?

    You really need to check with your datacenter and see what DNS resolvers you are suppose to be using. If you are using the correct ones that your datacenter says that you should be using, then you should point out that they are not resolving AOL's MX records properly.

    Alternatively, you can use OpenDNS's DNS servers, although if your datacenter has an in house DNS server, then it is probably best to use it.
     
  18. mtindor

    mtindor Well-Known Member

    Joined:
    Sep 14, 2004
    Messages:
    1,281
    Likes Received:
    37
    Trophy Points:
    48
    Location:
    inside a catfish
    cPanel Access Level:
    Root Administrator
    <SNIP>

    Ok, you did that - now do dig aol.com mx (all by itself) - Then compare it with dig aol.com mx @resolver.qwest.net. You'll see the difference. As they keep mentioning to you, you have a problem with your resolvers.

    Sparek-3 asked what you have in /etc/resolv.conf. One or both of the nameservers listed in your /etc/resolv.conf are either not resolving properly or are set up to not answer your queries. You must speak to your provider about that.

    When your machine attempts to look up the MX records for AOL.com, it contacts [or attempts to contact] the servers listed in your /etc/resolv.conf. If those resolvers don't have valid information [or won't return it because of the way they are configured], then you won't get any useful results when you do a dig either.

    Mike
     
  19. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16

    Below are conents of the /etc/resolv.conf

    [root@saturn ~]# vi /etc/resolv.conf
    nameserver 69.72.212.42
    nameserver 69.72.212.43
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    "/etc/resolv.conf" 2L, 48C
     
  20. Pixelpirat

    Pixelpirat Well-Known Member

    Joined:
    Jun 6, 2006
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Germany
    Both nameserver doesn't resolve any domain out of there authoritative domainzones.
    Use two other nameservers and ask your datacenter which a request forwarden to resolve the request.

    HTH
    Pixelpirat
     
Loading...

Share This Page