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

    false timestamp on reply flag

    Z-Push when using Kopano
    2
    4
    570
    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.
    • Coffee_is_life
      Coffee_is_life last edited by

      Hello Forum,

      searched a while but didnt find any topics about this:

      if i forward a mail from any folder, the replyflag is set and in Outlook it displays something like that:
      0_1531901348274_83ecd808-069d-4094-9921-79bd22c04591-grafik.png

      this is a timestamp in 2h future.
      The send item displays the right time - its just the flag and can lead to confusion.

      The KOE log displays the right time
      z-push-top displays the right time

      z-push-config.php:

       define('TIMEZONE', 'Europe/Berlin');
      

      mailserver got the right time aswell

      webapp also displays the right time:
      0_1531901551888_20715b9d-57a0-4477-83ae-76c3e72a3307-grafik.png

      is this an outlook internal error or can z-push cause this?

      coffee_is_life

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

        Hi coffee_is_life,

        I was able to reproduce the issue and we’re looking into it.

        Manfred

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

          Hello, any updates here or a ticket to follow the status?

          thanks in advance,

          coffee_is_life

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

            Hi coffee_is_life,

            there is a ticket https://jira.kopano.io/browse/KOE-175. The issue is fixed and should be in the next release.

            Manfred

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