Loading ...
Sorry, an error occurred while loading the content.

Lost connection

Expand Messages
  • Muzaffer Tolga Özses
    Hi, It seems my service provider s network has been blocked by Hotmail. After many correspondences, I was mailed by Hotmail that the issue was cleared for one
    Message 1 of 8 , Feb 27, 2013
    • 0 Attachment
      Hi,

      It seems my service provider's network has been blocked by Hotmail.
      After many correspondences, I was mailed by Hotmail that the issue was
      cleared for one IP, however I gave them wrong one. So, I edited main.cf
      and replaced inet_interfaces = all with inet_interfaces = the.ip.I.gave,
      and restarted postfix. However, I'm now getting "(connect to
      127.0.0.1[127.0.0.1]:10024: Connection refused)". I did a grep in the
      logs and the output was "Feb 27 09:48:17 server postfix/smtp[11674]:
      3C361768793: to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024,
      delay=0.04, delays=0.03/0.01/0/0, dsn=4.4.2, status=deferred (lost
      connection with 127.0.0.1[127.0.0.1] while receiving the initial server
      greeting)"

      My postconf -n:

      alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
      alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
      append_dot_mydomain = no
      biff = no
      body_checks = regexp:/etc/postfix/body_checks
      broken_sasl_auth_clients = yes
      config_directory = /etc/postfix
      content_filter = amavis:[127.0.0.1]:10024
      header_checks = regexp:/etc/postfix/header_checks
      html_directory = /usr/share/doc/postfix/html
      inet_interfaces = 5.9.235.23
      mailbox_size_limit = 0
      message_size_limit = 0
      mime_header_checks = regexp:/etc/postfix/mime_header_checks
      mydestination = server.ommuse.com, localhost, localhost.localdomain
      myhostname = server.ommuse.com
      mynetworks = 127.0.0.0/8 [::1]/128
      myorigin = /etc/mailname
      nested_header_checks = regexp:/etc/postfix/nested_header_checks
      owner_request_special = no
      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
      readme_directory = /usr/share/doc/postfix
      receive_override_options = no_address_mappings
      recipient_delimiter = +
      relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf
      relay_recipient_maps =
      mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
      relayhost =
      smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
      smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
      smtpd_client_message_rate_limit = 100
      smtpd_client_restrictions = check_client_access
      mysql:/etc/postfix/mysql-virtual_client.cf
      smtpd_recipient_restrictions = permit_mynetworks,
      permit_sasl_authenticated, check_recipient_access
      mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination
      smtpd_sasl_auth_enable = yes
      smtpd_sasl_authenticated_header = yes
      smtpd_sasl_path = private/auth
      smtpd_sasl_type = dovecot
      smtpd_sender_restrictions = check_sender_access
      mysql:/etc/postfix/mysql-virtual_sender.cf
      smtpd_tls_cert_file = /etc/postfix/smtpd.cert
      smtpd_tls_key_file = /etc/postfix/smtpd.key
      smtpd_tls_security_level = may
      smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
      smtpd_use_tls = yes
      transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
      virtual_alias_domains =
      virtual_alias_maps =
      proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf,
      proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf,
      hash:/var/lib/mailman/data/virtual-mailman
      virtual_gid_maps = static:5000
      virtual_mailbox_base = /var/vmail
      virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
      virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
      virtual_transport = dovecot
      virtual_uid_maps = static:5000

      What to do?
      Regards,
    • Wietse Venema
      ... http://www.postfix.org/DEBUG_README.html#logging When Postfix does not receive or deliver mail, the first order of business is to look for errors that
      Message 2 of 8 , Feb 27, 2013
      • 0 Attachment
        Muzaffer Tolga ?zses:
        > Hi,
        >
        > It seems my service provider's network has been blocked by Hotmail.
        > After many correspondences, I was mailed by Hotmail that the issue was
        > cleared for one IP, however I gave them wrong one. So, I edited main.cf
        > and replaced inet_interfaces = all with inet_interfaces = the.ip.I.gave,
        > and restarted postfix. However, I'm now getting "(connect to
        > 127.0.0.1[127.0.0.1]:10024: Connection refused)". I did a grep in the
        > logs and the output was "Feb 27 09:48:17 server postfix/smtp[11674]:
        > 3C361768793: to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024,
        > delay=0.04, delays=0.03/0.01/0/0, dsn=4.4.2, status=deferred (lost
        > connection with 127.0.0.1[127.0.0.1] while receiving the initial server
        > greeting)"

        http://www.postfix.org/DEBUG_README.html#logging

        When Postfix does not receive or deliver mail, the first order of
        business is to look for errors that prevent Postfix from working
        properly:

        % egrep '(warning|error|fatal|panic):' /some/log/file | more

        Note: the most important message is near the BEGINNING of the output.
        Error messages that come later are less useful.

        The nature of each problem is indicated as follows:

        * "panic" indicates a problem in the software itself that only a
        programmer can fix. Postfix cannot proceed until this is fixed.

        * "fatal" is the result of missing files, incorrect permissions,
        incorrect configuration file settings that you can fix. Postfix
        cannot proceed until this is fixed.

        * "error" reports an error condition. For safety reasons, a Postfix
        process will terminate when more than 13 of these happen.

        * "warning" indicates a non-fatal error. These are problems that
        you may not be able to fix (such as a broken DNS server elsewhere
        on the network) but may also indicate local configuration errors
        that could become a problem later.
      • Muzaffer Tolga Özses
        ... Unfortunately, all I get was these and similar, and the most recent one is from 2 days ago. egrep (warning|error|fatal|panic): /var/log/mail.log | head
        Message 3 of 8 , Feb 27, 2013
        • 0 Attachment
          On 02/27/2013 02:04 PM, Wietse Venema wrote:
          > egrep '(warning|error|fatal|panic):

          Unfortunately, all I get was these and similar, and the most recent one
          is from 2 days ago.

          egrep '(warning|error|fatal|panic):' /var/log/mail.log | head
          Feb 25 01:56:26 server postfix/smtpd[10324]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:28 server postfix/smtpd[10353]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:30 server postfix/smtpd[10354]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:32 server postfix/smtpd[10355]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:34 server postfix/smtpd[10356]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:36 server postfix/smtpd[10357]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:38 server postfix/smtpd[10358]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:40 server postfix/smtpd[10359]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:41 server postfix/smtpd[10360]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6
          Feb 25 01:56:42 server postfix/smtpd[10361]: warning:
          s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
          authentication failed: UGFzc3dvcmQ6

          Regards,
        • Reindl Harald
          ... well, is 213.165.85.151 the IP of a customer? has someone troubles? if not - ignore it because it s mostly some bad guy trying tu misuse your machine and
          Message 4 of 8 , Feb 27, 2013
          • 0 Attachment
            Am 27.02.2013 13:14, schrieb Muzaffer Tolga Özses:
            >
            > On 02/27/2013 02:04 PM, Wietse Venema wrote:
            >> egrep '(warning|error|fatal|panic):
            >
            > Unfortunately, all I get was these and similar, and the most recent one is from 2 days ago.
            >
            > egrep '(warning|error|fatal|panic):' /var/log/mail.log | head
            > Feb 25 01:56:26 server postfix/smtpd[10324]: warning: s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
            > authentication failed: UGFzc3dvcmQ6
            > Feb 25 01:56:28 server postfix/smtpd[10353]: warning: s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
            > authentication failed: UGFzc3dvcmQ6

            well, is 213.165.85.151 the IP of a customer?
            has someone troubles?

            if not - ignore it because it's mostly some bad guy trying
            tu misuse your machine and looking at the short interval
            it seems that it is the case
          • Simon Brereton
            ... UGFzc3dvcmQ6 is the hash for password. I have hundred of attempts like this on a daily basis. But as Wietse will point out, this is not his problem. Simon
            Message 5 of 8 , Feb 27, 2013
            • 0 Attachment
              On 27 February 2013 13:16, Reindl Harald <h.reindl@...> wrote:
              >
              >
              > Am 27.02.2013 13:14, schrieb Muzaffer Tolga Özses:
              >>
              >> On 02/27/2013 02:04 PM, Wietse Venema wrote:
              >>> egrep '(warning|error|fatal|panic):
              >>
              >> Unfortunately, all I get was these and similar, and the most recent one is from 2 days ago.
              >>
              >> egrep '(warning|error|fatal|panic):' /var/log/mail.log | head
              >> Feb 25 01:56:26 server postfix/smtpd[10324]: warning: s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
              >> authentication failed: UGFzc3dvcmQ6
              >> Feb 25 01:56:28 server postfix/smtpd[10353]: warning: s15313432.onlinehome-server.info[213.165.85.151]: SASL LOGIN
              >> authentication failed: UGFzc3dvcmQ6
              >
              > well, is 213.165.85.151 the IP of a customer?
              > has someone troubles?
              >
              > if not - ignore it because it's mostly some bad guy trying
              > tu misuse your machine and looking at the short interval
              > it seems that it is the case
              >

              UGFzc3dvcmQ6 is the hash for password. I have hundred of attempts
              like this on a daily basis.

              But as Wietse will point out, this is not his problem.

              Simon
            • Wietse Venema
              ... You have a service on 127.0.0.1 port 10024 that isn t receiving mail as it should. If that is not a Postfix service, then my trouble shooting egrep pattern
              Message 6 of 8 , Feb 27, 2013
              • 0 Attachment
                Wietse Venema:
                > > and restarted postfix. However, I'm now getting "(connect to
                > > 127.0.0.1[127.0.0.1]:10024: Connection refused)". I did a grep in the
                > > logs and the output was "Feb 27 09:48:17 server postfix/smtp[11674]:
                > > 3C361768793: to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024,
                > > delay=0.04, delays=0.03/0.01/0/0, dsn=4.4.2, status=deferred (lost
                > > connection with 127.0.0.1[127.0.0.1] while receiving the initial server
                > > greeting)"

                You have a service on 127.0.0.1 port 10024 that isn't receiving
                mail as it should. If that is not a Postfix service, then my
                trouble shooting egrep pattern will not apply.

                Wietse
              • Muzaffer Tolga Özses
                ... I had stopped amavis while trying to debug. I now started it again, and now I am getting Feb 27 16:13:51 server postfix/smtp[18445]: 71D347687A4:
                Message 7 of 8 , Feb 27, 2013
                • 0 Attachment
                  On 02/27/2013 04:04 PM, Wietse Venema wrote:
                  > Wietse Venema:
                  >>> and restarted postfix. However, I'm now getting "(connect to
                  >>> 127.0.0.1[127.0.0.1]:10024: Connection refused)". I did a grep in the
                  >>> logs and the output was "Feb 27 09:48:17 server postfix/smtp[11674]:
                  >>> 3C361768793: to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024,
                  >>> delay=0.04, delays=0.03/0.01/0/0, dsn=4.4.2, status=deferred (lost
                  >>> connection with 127.0.0.1[127.0.0.1] while receiving the initial server
                  >>> greeting)"
                  > You have a service on 127.0.0.1 port 10024 that isn't receiving
                  > mail as it should. If that is not a Postfix service, then my
                  > trouble shooting egrep pattern will not apply.
                  >
                  > Wietse
                  I had stopped amavis while trying to debug. I now started it again, and
                  now I am getting
                  "Feb 27 16:13:51 server postfix/smtp[18445]: 71D347687A4:
                  to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.02,
                  delays=0/0.01/0.01/0, dsn=4.4.2, status=deferred (lost connection with
                  127.0.0.1[127.0.0.1] while receiving the initial server greeting)"

                  M.
                • Wietse Venema
                  ... Apparently, Amavis isn t receiving mail as it should. That is outside my area of support. Wietse
                  Message 8 of 8 , Feb 27, 2013
                  • 0 Attachment
                    Wietse:
                    > You have a service on 127.0.0.1 port 10024 that isn't receiving
                    > mail as it should. If that is not a Postfix service, then my
                    > trouble shooting egrep pattern will not apply.

                    Muzaffer Tolga ?zses:
                    > I had stopped amavis while trying to debug. I now started it again, and
                    > now I am getting
                    > "Feb 27 16:13:51 server postfix/smtp[18445]: 71D347687A4:
                    > to=<tolga@...>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.02,
                    > delays=0/0.01/0.01/0, dsn=4.4.2, status=deferred (lost connection with
                    > 127.0.0.1[127.0.0.1] while receiving the initial server greeting)"

                    Apparently, Amavis isn't receiving mail as it should. That is outside
                    my area of support.

                    Wietse
                  Your message has been successfully submitted and would be delivered to recipients shortly.