Email delivery problem - Ubuntu Karmic Koala (Ubuntu 9.10) [ISPConfig 2]

Discussion in 'General' started by qiubosu, Jan 18, 2010.

  1. qiubosu

    qiubosu New Member

    Dear Sir/Madam,

    I followed Falko Timme's tutorial of "The Perfect Server - Ubuntu Karmic
    Koala (Ubuntu 9.10) [ISPConfig 2]" to setup the ISP web hosting system, ISPConfig 2 and Squirrelmail, but I have problem when testing the email (in ISPConfig 2, create client, website, user & mail for squirrelmail etc before testing the email):

    1. in Ubuntu prompt, run "mail root" to send email message to my personal
    email address qiubosu@gmail.com, to email address root@qiubosu.dyndns.org created in ISPConfig 2 for the user & mail. But the email message could neither be received from qiubosu@gmail.com nor root@qiubosu.dyndns.org.

    2. login into Squirrlemail webmail interface and sent email message to my
    personal email address qiubosu@gmail.com, but the email message couldn't be received from qiubosu@gmail.com as well.

    3. from qiubosu@gmail.com, sent email message to root@qiubosu.dyndns.org, but the email message couldn't be received in root@qiubosu.dyndns.org.

    In all, the email message delivery into and out the email system hasn't been
    worked so far.

    It is much appreciated if anyone can help with this, e.g. the information
    guidance to identify and solve the problem; the approach to test each
    part/server in the email delivery chain to discover the issue; whatever
    helpful approach/method.
     
  2. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Any errors in your mail log?
     
  3. qiubosu

    qiubosu New Member

    hello falko,

    thank you very much for the help. i have been working on other thing and just got the chance to reply you.

    after i run the below commands in the Ubuntu terminal

    mail root
    Cc: qiubosu@gmail.com
    Subject: test
    .

    i got below output log in the /var/log/mail.log file. how do you identify the issues from the below log?

    Jan 26 19:10:12 smartracksolutions postfix/pickup[2478]: D1E5A1B71: uid=0 from=<root>
    Jan 26 19:10:12 smartracksolutions postfix/cleanup[2543]: D1E5A1B71: message-id=<20100126061012.D1E5A1B71@smartracksolutions.dyndns.org>
    Jan 26 19:10:12 smartracksolutions postfix/qmgr[2479]: D1E5A1B71: from=<root@smartracksolutions.dyndns.org>, size=409, nrcpt=2 (queue active)
    Jan 26 19:10:13 smartracksolutions postfix/smtpd[2547]: connect from localhost.localdomain[127.0.0.1]
    Jan 26 19:10:13 smartracksolutions postfix/trivial-rewrite[2545]: warning: do not list domain smartracksolutions.dyndns.org in BOTH mydestination and virtual_mailbox_domains
    Jan 26 19:10:13 smartracksolutions postfix/smtpd[2547]: BC5CC1E1F: client=localhost.localdomain[127.0.0.1]
    Jan 26 19:10:13 smartracksolutions postfix/cleanup[2543]: BC5CC1E1F: message-id=<20100126061012.D1E5A1B71@smartracksolutions.dyndns.org>
    Jan 26 19:10:13 smartracksolutions postfix/qmgr[2479]: BC5CC1E1F: from=<root@smartracksolutions.dyndns.org>, size=866, nrcpt=2 (queue active)
    Jan 26 19:10:13 smartracksolutions postfix/smtpd[2547]: disconnect from localhost.localdomain[127.0.0.1]
    Jan 26 19:10:13 smartracksolutions postfix/trivial-rewrite[2545]: warning: do not list domain smartracksolutions.dyndns.org in BOTH mydestination and virtual_mailbox_domains
    Jan 26 19:10:13 smartracksolutions amavis[1186]: (01186-02) Passed CLEAN, <root@smartracksolutions.dyndns.org> -> <qiubosu@gmail.com>,<root@smartracksolutions.dyndns.org>, Message-ID: <20100126061012.D1E5A1B71@smartracksolutions.dyndns.org>, mail_id: qgpxSjDy3b9K, Hits: 2.794, size: 409, queued_as: BC5CC1E1F, 902 ms
    Jan 26 19:10:13 smartracksolutions postfix/smtp[2546]: D1E5A1B71: to=<qiubosu@gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.21/0.05/0.01/0.94, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=01186-02, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as BC5CC1E1F)
    Jan 26 19:10:13 smartracksolutions postfix/smtp[2546]: D1E5A1B71: to=<root@smartracksolutions.dyndns.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.21/0.05/0.01/0.94, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=01186-02, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as BC5CC1E1F)
    Jan 26 19:10:13 smartracksolutions postfix/qmgr[2479]: D1E5A1B71: removed
    Jan 26 19:10:14 smartracksolutions postfix/smtpd[2523]: warning: 125.236.178.150: address not listed for hostname dsldevice.lan
    Jan 26 19:10:14 smartracksolutions postfix/smtpd[2523]: connect from unknown[125.236.178.150]
    Jan 26 19:10:14 smartracksolutions postfix/smtp[2549]: warning: host smartracksolutions.dyndns.org[125.236.178.150]:25 greeted me with my own hostname smartracksolutions.dyndns.org
    Jan 26 19:10:14 smartracksolutions postfix/smtp[2549]: warning: host smartracksolutions.dyndns.org[125.236.178.150]:25 replied to HELO/EHLO with my own hostname smartracksolutions.dyndns.org
    Jan 26 19:10:14 smartracksolutions postfix/smtp[2549]: BC5CC1E1F: to=<root@smartracksolutions.dyndns.org>, relay=smartracksolutions.dyndns.org[125.236.178.150]:25, delay=0.61, delays=0.12/0.16/0.33/0, dsn=5.4.6, status=bounced (mail for smartracksolutions.dyndns.org loops back to myself)
    Jan 26 19:10:14 smartracksolutions postfix/smtpd[2523]: disconnect from unknown[125.236.178.150]
    Jan 26 19:10:33 smartracksolutions postfix/smtp[2482]: connect to alt3.gmail-smtp-in.l.google.com[209.85.219.25]:25: Connection timed out
    Jan 26 19:10:33 smartracksolutions postfix/smtp[2484]: connect to alt3.gmail-smtp-in.l.google.com[209.85.219.25]:25: Connection timed out
    Jan 26 19:10:44 smartracksolutions postfix/smtp[2548]: connect to gmail-smtp-in.l.google.com[209.85.222.94]:25: Connection timed out
    Jan 26 19:11:03 smartracksolutions postfix/smtp[2482]: connect to alt4.gmail-smtp-in.l.google.com[209.85.220.17]:25: Connection timed out
    Jan 26 19:11:03 smartracksolutions postfix/smtp[2484]: connect to alt4.gmail-smtp-in.l.google.com[209.85.220.17]:25: Connection timed out
    Jan 26 19:11:03 smartracksolutions postfix/smtp[2482]: A8E158402: to=<qiubosu@gmail.com>, relay=none, delay=2055, delays=1904/0.24/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[209.85.220.17]:25: Connection timed out)
    Jan 26 19:11:03 smartracksolutions postfix/smtp[2484]: AD348642A: to=<qiubosu@gmail.com>, relay=none, delay=2659, delays=2508/0.23/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[209.85.220.17]:25: Connection timed out)
    Jan 26 19:11:14 smartracksolutions postfix/smtp[2548]: connect to alt1.gmail-smtp-in.l.google.com[209.85.211.82]:25: Connection timed out
     
  4. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Is it possible that you used the tutorial for ISPConfig 3 instead of ISPConfig 2?
    What's in /etc/postfix/main.cf?
     
  5. qiubosu

    qiubosu New Member

    hello falko,

    this one is for ispconfig 3. i installed both ispconfig 2 & 3. the original post is for ispconfig 2. but when i tested the email for ispconfig 3, it doesn't work as well, so i replied you with the mail.log file when i tested the email under ispconfig 3.

    the /etc/postfix/main.cf for ispconfig 3 is as below:

    # See /usr/share/postfix/main.cf.dist for a commented, more complete version


    # Debian specific: Specifying a file name will cause the first
    # line of that file to be used as the name. The Debian default
    # is /etc/mailname.
    #myorigin = /etc/mailname

    smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
    biff = no

    # appending .domain is the MUA's job.
    append_dot_mydomain = no

    # Uncomment the next line to generate "delayed mail" warnings
    #delay_warning_time = 4h

    readme_directory = /usr/share/doc/postfix

    # TLS parameters
    smtpd_tls_cert_file = /etc/postfix/smtpd.cert
    smtpd_tls_key_file = /etc/postfix/smtpd.key
    smtpd_use_tls = yes
    smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
    smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

    # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
    # information on enabling SSL in the smtp client.

    myhostname = smartracksolutions.dyndns.org
    alias_maps = hash:/etc/aliases
    alias_database = hash:/etc/aliases
    myorigin = /etc/mailname
    mydestination = smartracksolutions.dyndns.org, localhost, localhost.localdomain
    relayhost = [192.168.1.64]:submission
    smtp_sasl_auth_enable = yes
    smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
    smtp_sasl_security_options = noanonymous
    smtp_use_tls = yes
    mynetworks = 127.0.0.0/8 [::1]/128
    mailbox_size_limit = 0
    recipient_delimiter = +
    inet_interfaces = all
    html_directory = /usr/share/doc/postfix/html
    virtual_alias_domains =
    virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf
    virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
    virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
    virtual_mailbox_base = /var/vmail
    virtual_uid_maps = static:5000
    virtual_gid_maps = static:5000
    smtpd_sasl_auth_enable = yes
    broken_sasl_auth_clients = yes
    smtpd_sasl_authenticated_header = yes
    smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination
    smtpd_tls_security_level = may
    transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
    relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf
    virtual_create_maildirsize = yes
    virtual_maildir_extended = yes
    virtual_mailbox_limit_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailbox_limit_maps.cf
    virtual_mailbox_limit_override = yes
    virtual_maildir_limit_message = "The user you are trying to reach is over quota."
    virtual_overquota_bounce = yes
    proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps
    smtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/mysql-virtual_sender.cf
    smtpd_client_restrictions = check_client_access mysql:/etc/postfix/mysql-virtual_client.cf
    maildrop_destination_concurrency_limit = 1
    maildrop_destination_recipient_limit = 1
    virtual_transport = maildrop
    header_checks = regexp:/etc/postfix/header_checks
    mime_header_checks = regexp:/etc/postfix/mime_header_checks
    nested_header_checks = regexp:/etc/postfix/nested_header_checks
    body_checks = regexp:/etc/postfix/body_checks
    content_filter = amavis:[127.0.0.1]:10024
    receive_override_options = no_address_mappings
    message_size_limit = 0
     
  6. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    I hope you formatted the server adter you installed one ispconfig version? If not, the system will not work. You can noz install ispconfig 2 on a system were ispconfig 3 was installed before and vice versa without a complete reinstall of the operating system.
     
  7. qiubosu

    qiubosu New Member

    Email delivery problem - Ubuntu Karmic Koala (Ubuntu 9.10) [ISPConfig 3]

    dear sir,

    the ispconfig 2, ispconfig 3 are installed in two different servers. the above /etc/postfix/main.cf file is for the ispconfig 3 installed in its own server. the mail.log file, post at 26th January 2010 19:25, is for the ispconfig 3 as well.

    your help with these 2 post again is much appreciated.

    thanks,
    d.s.
     
  8. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    We should concentrate on one server. Since your first post was about ISPConfig 2, please post the mail log from your ISPConfig 2 server.
     
  9. qiubosu

    qiubosu New Member

    dear falko,

    as you suggested, i did another test under ispconfig 2 server:

    mail root
    Subject: test
    test
    .
    Cc: qiubosu@gmail.com

    below is the main.log for this test:

    Jan 29 07:41:34 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:41:34 smartrack imapd: LOGOUT, ip=[::ffff:127.0.0.1], rcvd=30, sent=470
    Jan 29 07:43:43 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:43:43 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41636], protocol=IMAP
    Jan 29 07:43:43 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=30, sent=238, time=0
    Jan 29 07:43:44 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:43:44 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41637], protocol=IMAP
    Jan 29 07:43:44 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=113, sent=261, time=0
    Jan 29 07:43:44 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:43:44 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41638], protocol=IMAP
    Jan 29 07:43:44 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=77, sent=419, time=0
    Jan 29 07:46:59 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:46:59 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41639], protocol=IMAP
    Jan 29 07:46:59 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=113, sent=261, time=0
    Jan 29 07:47:21 smartrack postfix/pickup[6515]: 84FA68F62: uid=0 from=<root>
    Jan 29 07:47:21 smartrack postfix/cleanup[6771]: 84FA68F62: message-id=<20100128184721.84FA68F62@smartrack.dyndns.org>
    Jan 29 07:47:21 smartrack postfix/qmgr[6332]: 84FA68F62: from=<root@smartrack.dyndns.org>, size=339, nrcpt=2 (queue active)
    Jan 29 07:47:21 smartrack postfix/pickup[6515]: C6BC78F6C: uid=10018 from=<web15_admin>
    Jan 29 07:47:21 smartrack postfix/local[6773]: 84FA68F62: to=<web15_admin@smartrack.dyndns.org>, orig_to=<root>, relay=local, delay=0.33, delays=0.1/0.05/0/0.17, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -f-)
    Jan 29 07:47:21 smartrack postfix/cleanup[6771]: C6BC78F6C: message-id=<20100128184721.C6BC78F6C@smartrack.dyndns.org>
    Jan 29 07:47:21 smartrack postfix/qmgr[6332]: C6BC78F6C: from=<web15_admin@smartrack.dyndns.org>, size=391, nrcpt=1 (queue active)
    Jan 29 07:47:21 smartrack postfix/local[6773]: C6BC78F6C: to=<admispconfig@localhost.localdomain>, relay=local, delay=0.18, delays=0.08/0/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -f-)
    Jan 29 07:47:21 smartrack postfix/qmgr[6332]: C6BC78F6C: removed
    Jan 29 07:47:25 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:47:25 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41641], protocol=IMAP
    Jan 29 07:47:25 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=113, sent=259, time=0
    Jan 29 07:47:27 smartrack imapd: Connection, ip=[::ffff:127.0.0.1]
    Jan 29 07:47:27 smartrack imapd: LOGIN, user=web15_admin, ip=[::ffff:127.0.0.1], port=[41642], protocol=IMAP
    Jan 29 07:47:27 smartrack imapd: LOGOUT, user=web15_admin, ip=[::ffff:127.0.0.1], headers=51, body=0, rcvd=222, sent=713, time=0
    Jan 29 07:47:54 smartrack postfix/smtp[6774]: connect to gmail-smtp-in.l.google.com[209.85.222.21]:25: Connection timed out
    Jan 29 07:48:24 smartrack postfix/smtp[6774]: connect to alt1.gmail-smtp-in.l.google.com[209.85.211.32]:25: Connection timed out
    Jan 29 07:48:54 smartrack postfix/smtp[6774]: connect to alt2.gmail-smtp-in.l.google.com[209.85.221.14]:25: Connection timed out

    below is the /etc/postfix/main.cf for this ispconfig 2 server:

    # See /usr/share/postfix/main.cf.dist for a commented, more complete version


    # Debian specific: Specifying a file name will cause the first
    # line of that file to be used as the name. The Debian default
    # is /etc/mailname.
    #myorigin = /etc/mailname

    smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
    biff = no

    # appending .domain is the MUA's job.
    append_dot_mydomain = no

    # Uncomment the next line to generate "delayed mail" warnings
    #delay_warning_time = 4h

    readme_directory = no

    # TLS parameters
    smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
    smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
    smtpd_use_tls = yes
    smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
    smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

    # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
    # information on enabling SSL in the smtp client.

    myhostname = smartrack.dyndns.org
    alias_maps = hash:/etc/aliases
    alias_database = hash:/etc/aliases
    myorigin = /etc/mailname
    mydestination = /etc/postfix/local-host-names
    relayhost =
    smtp_sasl_auth_enable = yes
    smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
    smtp_sasl_security_options = noanonymous
    mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
    mailbox_command = procmail -a "$EXTENSION"
    mailbox_size_limit = 0
    recipient_delimiter = +
    inet_interfaces = all
    inet_protocols = all
    smtpd_sasl_local_domain =
    smtpd_sasl_auth_enable = yes
    smtpd_sasl_security_options = noanonymous
    broken_sasl_auth_clients = yes
    smtpd_sasl_authenticated_header = yes
    smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
    smtpd_tls_auth_only = no
    smtp_use_tls = yes
    smtp_tls_note_starttls_offer = yes
    smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
    smtpd_tls_loglevel = 1
    smtpd_tls_received_header = yes
    smtpd_tls_session_cache_timeout = 3600s
    tls_random_source = dev:/dev/urandom

    virtual_maps = hash:/etc/postfix/virtusertable

    mydestination = /etc/postfix/local-host-names
     
  10. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Please check if your server is blacklisted: http://mxtoolbox.com/blacklists.aspx
     
  11. qiubosu

    qiubosu New Member

    hello falko,

    i ran a "blacklist" for smartrack.dyndns.org in http://mxtoolbox.com/blacklists.aspx and got the below return:

    blacklist:smartrack.dyndns.org blacklist

    We notice you are on a blacklist. Click here for some suggestions

    smartrack.dyndns.org was resolved to 125.236.178.150.
    Checking smartrack.dyndns.org against 104 known blacklists...
    Listed 2 times with 3 timeouts.

    Blacklist Status Reason TTL ResponseTime

    Spamhaus-ZEN LISTED Detail
    Return codes were: 127.0.0.10 514 187

    UCEPROTECTL3 LISTED Your ISP NZTELECOM Netgate/AS4771 is UCEPROTECT-Level3 listed for hosting a total of 2418 abusers. See: Detail
    Return codes were: 127.0.0.2 1715 78

    it is much appreciated if you can provide information on how to get the issues sorted.

    thanks.
     
  12. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Are you on a dynamic IP? Most dynamic IPs are blacklisted, and there's nothing you can do about it...
     
  13. qiubosu

    qiubosu New Member

    hello falko,

    yes, i use dynamic ip. actually i have thought about that the problem might be caused by using the dynamic ip and i just want to swap it to static ip.

    thanks
     
  14. qiubosu

    qiubosu New Member

    hello falko,

    for solving the problem, except of swapping dynamic ip address to static ip address, are there any other solutions instead of using static ip address?

    at the moment, it is just in the stage to test the isp hosting server, not yet in production yet, so it may not really need a static ip address now.

    your help is much appreciated.

    thanks,
    d.s.
     
  15. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

  16. qiubosu

    qiubosu New Member

    hello falko,

    applied a static ip from ISP, the email send & receive is ok now. but when doing a blacklist through "http://mxtoolbox.com/blacklists.aspx" with the static ip address, got the below return. does this matter?

    blacklist:219.88.70.31 blacklist

    We notice you are on a blacklist. Click here for some suggestions

    Checking 219.88.70.31 against 104 known blacklists...
    Listed 1 times with 3 timeouts.

    Blacklist Status Reason TTL ResponseTime

    NOMOREFUNN LISTED smtp.mcgirr.co.nz. Dynamic IP or generic rDNS. Use your ISPs mail service, or whitelist at: Detail 1159963186 #
    Return codes were: 127.0.0.3 2100 499
     
  17. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    Yes, this could be a problem. You can ask the blacklist maintainer to remove you from the list because you have a static IP.
     
  18. qiubosu

    qiubosu New Member

    hello falko,

    i did another blacklist test for my static ip address 219.88.70.31, but get the same outputs (shown below) as those for the previous dynamic ip address (the one before i applied for a static ip address). so, there is no improvement when changing to static ip address from dynamic ip address. any idea?

    blacklist:219.88.70.31 blacklist

    We notice you are on a blacklist. Click here for some suggestions


    Checking 219.88.70.31 against 104 known blacklists...
    Listed 2 times with 4 timeouts.
    Blacklist Status Reason TTL ResponseTime
    NOMOREFUNN LISTED smtp.mcgirr.co.nz. Dynamic IP or generic rDNS. Use your ISPs mail service, or whitelist at: Detail 1159963186 #
    Return codes were: 127.0.0.3 2100 889
    UCEPROTECTL3 LISTED Your ISP NZTELECOM Netgate/AS4771 is UCEPROTECT-Level3 listed for hosting a total of 3399 abusers. See: Detail
    Return codes were: 127.0.0.2 2100 889
     
  19. qiubosu

    qiubosu New Member

    hello falko,

    moreover, when using static ip address, sending email from & to ispconfig server isn't ok at the moment (port 25 open), the same as when using the dynamic ip address. but when just swapping from dynamic ip address to static ip address, sending email from & to ispconfig server was ok before (haven't done any change/update with the ispconfig server since swapping to static ip address). any idea on this?

    thanks
     
  20. falko

    falko Super Moderator Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    It seems as if the static IP given to you by your ISP is from dynamic IP pool and therefore blacklisted. I doubt that you can do anything about it.
     

Share This Page