Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Not possible to receive e-mails with more than 19500 characters in the message body

    Kopano Groupware Core
    2
    5
    514
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • macduke
      macduke last edited by

      Hello,

      my kopano installation works fine, only if i get messages longer than 19500 characters, kopano does not accept the postfix email and

      "Mailbox temporarily unavailable (in reply to end of DATA command)"
      

      appears in the postquere.

      In the Kopano server log appears

      "Sun Jul 15 11:47:48 2018: [warning] SQL[00000480] info: Try to reconnect
      Sun Jul 15 11:47:48 2018: [error]  SQL[00000481] Failed: MySQL server has gone away, Query Size: 28757, Query: "REPLACE INTO properties (hierarchyid,tag,type,properties.val_ulong,properties.val_string,properties.val_binary,properties.val_double,properties.val_longint,properties.val_hi,properties.val_lo) VALUES(1487,34054,30,null,'ClamAV using ClamSMTP',null,null,null,null,null,null,null),(1487,34056,30,null,'\"Sun, 15 Jul 2018 11:47:41 +0200\") \"19500\" "...
      

      In the dagent Log:

      Sun Jul 15 12:04:34 2018: [error  ] [ 1182] Unable to commit message: disk error (80040116)
      Sun Jul 15 12:04:34 2018: [error  ] [ 1182] Unable to deliver message to "myuser", error code: 0x80040116
      Sun Jul 15 12:04:34 2018: [error  ] [ 1182] Unable to deliver all messages for server "file:///var/run/kopano/server.sock"
      

      The mysql and the kopano server run both under debian 9.

      The mysql server packages:

      ii  dbconfig-mysql                    2.0.8                          all          dbconfig-common MySQL/MariaDB support
      ii  default-mysql-client              1.0.2                          all          MySQL database client binaries (metapackage)
      ii  libdbd-mysql-perl                 4.041-2                        amd64        Perl5 database interface to the MariaDB/MySQL database
      ii  libmariadbclient18:amd64          10.1.26-0+deb9u1               amd64        MariaDB database client library
      ii  libmysqlclient18:amd64            5.5.54-0+deb8u1                amd64        MySQL database client library
      ii  mariadb-client-10.1               10.1.26-0+deb9u1               amd64        MariaDB database client binaries
      ii  mariadb-client-core-10.1          10.1.26-0+deb9u1               amd64        MariaDB database core client binaries
      ii  mariadb-common                    10.1.26-0+deb9u1               all          MariaDB common metapackage
      ii  mariadb-server                    10.1.26-0+deb9u1               all          MariaDB database server (metapackage depending on the latest version)
      ii  mariadb-server-10.1               10.1.26-0+deb9u1               amd64        MariaDB database server binaries
      ii  mariadb-server-core-10.1          10.1.26-0+deb9u1               amd64        MariaDB database core server files
      ii  mysql-common                      5.8+1.0.2                      all          MySQL database common files, e.g. /etc/mysql/my.cnf
      ii  php-mysql                         1:7.0+49                       all          MySQL module for PHP [default]
      ii  php5-mysql                        5.6.30+dfsg-0+deb8u1           amd64        MySQL module for php5
      ii  php7.0-mysql                      7.0.30-0+deb9u1                amd64        MySQL module for PHP
      

      I already changed the max_allowed_packet to 128M but didnt changed anything. I never had this problem with the zarafa installation.

      Many thanks for any help!
      macduke

      fbartels 1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano @macduke last edited by fbartels

        @macduke which version of Kopano are you running? Did you try updating to the latest release?

        Edit: to clarify this sounds like a issue in early Debian 9 builds that has long since been fixed.

        Regards Felix

        Resources:
        https://kopano.com/blog/how-to-get-kopano/
        https://documentation.kopano.io/
        https://kb.kopano.io/

        Support overview:
        https://kopano.com/support/

        1 Reply Last reply Reply Quote 0
        • macduke
          macduke last edited by

          @fbartels thx for your reply. The dpkg-query shows “kopano-server 8.4.90.1513-0+172.1”.

          Regards Thorsten

          1 Reply Last reply Reply Quote 0
          • fbartels
            fbartels Kopano last edited by

            @macduke that version is ancient. We are at 8.6.80.1248 meanwhile.

            Regards Felix

            Resources:
            https://kopano.com/blog/how-to-get-kopano/
            https://documentation.kopano.io/
            https://kb.kopano.io/

            Support overview:
            https://kopano.com/support/

            1 Reply Last reply Reply Quote 0
            • macduke
              macduke last edited by

              Thx a lot. I updated and now it is working !

              1 Reply Last reply Reply Quote 0
              • First post
                Last post