Mail is not receiving to my squirellmail

Discussion in 'Installation/Configuration' started by Hariharan G, Feb 23, 2015.

  1. Hariharan G

    Hariharan G New Member

    Hi, I had installed my ubuntu server from scratch using this link.
    https://www.howtoforge.com/perfect-...sl-pureftpd-bind-postfix-doveot-and-ispconfig

    Now I am able to send mails to other domains but not able to receive mails. I got the below error
    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the server for the recipient domain hardcube.net by smtp.europe.secureserver.net. [188.121.52.56].

    So please help me to solve this issue.

    Thanks in advance.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    and the IP in the message is your server IP?
     
  3. Hariharan G

    Hariharan G New Member

    No, that is not my server ip
     
  4. Hariharan G

    Hariharan G New Member

    ~$ telnet mail.hardcube.net 143
    Trying 117.218.121.123...
    telnet: Unable to connect to remote host: Connection refused

    Im getting the above error for 110 also.

    Can you help me to solve this issue.
    I think because of that only I am not able to receive the mails.
     
  5. Hariharan G

    Hariharan G New Member

    Below is the output of netstat -nl4

    $ netstat -nl4
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
    tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN
    tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN
    tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:3690 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN
    tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
    tcp 0 0 192.168.2.6:53 0.0.0.0:* LISTEN
    tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
    udp 0 0 127.0.0.1:11211 0.0.0.0:*
    udp 0 0 192.168.2.6:53 0.0.0.0:*
    udp 0 0 127.0.0.1:53 0.0.0.0:*
    udp 0 0 192.168.2.6:123 0.0.0.0:*
    udp 0 0 127.0.0.1:123 0.0.0.0:*
    udp 0 0 0.0.0.0:123 0.0.0.0:*
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, so its not a problem with your server. You should check the dns record of your domain and ensure that the MX record points to a DNS A-Record which points to the IP address of your server and not to that other IP.
     
  7. Hariharan G

    Hariharan G New Member

    Hi,
    I have attached the screenshot of the DNS-A record.
     

    Attached Files:

  8. Hariharan G

    Hariharan G New Member

    And this is my ifconfig
    $ ifconfig
    eth0 Link encap:Ethernet HWaddr 70:54:d2:7b:8b:f0
    inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::7254:d2ff:fe7b:8bf0/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:39889 errors:0 dropped:1 overruns:0 frame:0
    TX packets:30835 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:30076549 (30.0 MB) TX bytes:9159773 (9.1 MB)
    Interrupt:20 Memory:f7c00000-f7c20000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:10642 errors:0 dropped:0 overruns:0 frame:0
    TX packets:10642 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2490007 (2.4 MB) TX bytes:2490007 (2.4 MB)
     
  9. Hariharan G

    Hariharan G New Member

    $ cat /etc/hosts
    127.0.0.1 localhost
    127.0.1.1 hardcube.net hardcube
    # The following lines are desirable for IPv6 capable hosts
    ::1 localhost ip6-localhost ip6-loopback
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters

    $ cat /etc/hostname
    hardcube
     
  10. Thedan04

    Thedan04 New Member

    Your domain hardcube.net Name Servers are listed as the godaddy nameservers when I use dig to determine what the authoritative nameservers are:
    $ dig +short hardcube.net NS
    ns12.domaincontrol.com.
    ns11.domaincontrol.com
    Godaddy DNS servers report the following MX records:
    $ dig +short @ns12.domaincontrol.com hardcube.net MX
    0 smtp.europe.secureserver.net.
    10 mailstore1.europe.secureserver.net

    The secureserver servers are godaddy servers, which are not configured to handle mail for your domain.

    The DNS values that you have configured in your server are only going to work locally for you, if you have configured your computers to use your local DNS server for these lookups. Any external server attempting to perform a lookup of any DNS record for your domain will use the records that exist in Godaddy's servers.
     
  11. Hariharan G

    Hariharan G New Member

    So, what should I do to make it work.
     
  12. Hariharan G

    Hariharan G New Member

    Can I know this DNS - A record is correct.
     

    Attached Files:

  13. Thedan04

    Thedan04 New Member

    If 166.62.12.213 was the IP address of your server when the screenshot was taken, then yes that would be correct. Mail would actually be delivered to the IP address listed as the "MX" record. If no MX record exists, I believe mail delivery may fall back to the "A" record.

    Verify the IP address that you want to receive mail at (the external IP address of your mail server).
    Verify that there is no firewall restricting access to that IP address and port combination (smtp is traditionally on port 25, Many ISP's block this port to help prevent spam and other attacks against mail servers.)
    Set the MX record for your domain to be the IP address of your mail server.
    Use dns tools such as "dig" or "nslookup" to verify that the changes have gone live.

    Test mail delivery.
     

Share This Page