Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: [SOLVED] 6.0.4 IMAP: Cannot copy mail to sent folder

  1. #21
    Join Date
    Jun 2008
    Location
    Utah, USA
    Posts
    11
    Rep Power
    7

    Default

    Looks like this issue is a duplicate of bug number 43359, which was resolved and closed on 12/10/2009 (?).

    I then checked the PM tool, and bug neither bug 43359 or bug 43669 have been added to a future release.

    Keeping my fingers crossed that there is a hotfix forthcoming....

    QWade

  2. #22
    Join Date
    Jan 2008
    Location
    Berlin, Germany
    Posts
    203
    Rep Power
    7

    Thumbs down

    Just got feedback from Zimbra Support:

    Unfortunately there is no hotfix available for this bug. The bug has been fixed and the fix is going to be available in ZCS 6.0.5.

    As we do not know the release date for ZCS 6.0.5 I cannot assure you any time frame but we expect it soon.
    :-((

    Regards

    Andreas

  3. #23
    Join Date
    Jan 2008
    Location
    Berlin, Germany
    Posts
    203
    Rep Power
    7

    Default

    ... since there's no help from Zimbra support yet I digged into the sourcecode and checked out what was causing this error. Bug 43669 has been marked as a duplicate of Bug 43359. I checked this bug out and found a workaround.

    The incorrect behaviour is triggered by Zimbra Message Store Blob compression not getting the correct message size to decide wether or not to compress it.

    Since we do not know a date for 6.0.5 I tried to determine a workaround and finally found a solution to avoid this error:

    Blob Compression is enabled by default for each message store and is been triggered by a treshold > 8kByte. So either disabling Blob compression or setting the blob compression treshold to a higher value is a temporary fix for this error.

    Disabling blob compression can be done by

    Code:
    zmvolume --name message1 --id 1 --edit --compress false
    Do a zmvolume --list first to detect the correct values for --name and --id.

    It should be safe to enable / disable Blob compression if disk space is not a major concern. The setting is being applied in the fly so there is no need to restart servers or services.

    At least this works for me. I hope this will help others too to get IMAP back to work until 6.0.5 is out.

    Regards

    Andreas
    Last edited by FritzBrause; 01-06-2010 at 01:35 AM.

  4. #24
    Join Date
    Jan 2010
    Posts
    5
    Rep Power
    5

    Default

    Quote Originally Posted by FritzBrause View Post
    ... since there's no help from Zimbra support yet I digged into the sourcecode
    Thansk for the work FritzBrause, I've applied your workaround and things are working again.

    Where do we send out next cheque for Zimbra support? (j/k).

  5. #25
    Join Date
    Dec 2009
    Posts
    30
    Rep Power
    6

    Thumbs down

    Quote Originally Posted by FritzBrause View Post
    It should be safe to enable / disable Blob compression if disk space is not a major concern. The setting is being applied in the fly so there is no need to restart servers or services.
    I have a question: if we disable compression now and reenable it when the bug is formally fixed, will enabling compression retroactively compress data that's currently uncompressed?

    Thanks for this, by the way. I just tried it and it seems to have resolved the issue for me.

  6. #26
    Join Date
    Jan 2008
    Location
    Berlin, Germany
    Posts
    203
    Rep Power
    7

    Default

    Quote Originally Posted by psarhjinian View Post
    I have a question: if we disable compression now and reenable it when the bug is formally fixed, will enabling compression retroactively compress data that's currently uncompressed?
    Blob compression is being done on demand. I you disable Blob compression all new data wil be stored as uncompressed data. When you re-enable compression existing blobs aren't touched but all new data exeeding "compressionThreshold" (4k default) will be stored as compressed Blob again.

    If you want to re-compress all existing data on a message store there are several ways to do this. e.g. moving the Message store by enabling HSM.
    There's also a bug / feature request Bug 35143 – blob compress and decompress tool

    Regards

    Andreas

  7. #27
    Join Date
    Jan 2008
    Location
    Berlin, Germany
    Posts
    203
    Rep Power
    7

    Default

    ... just checked with one server upgraded to 6.0.5: Blob compression enabled again an no issues with IMAP / Attachments so far. Everything is working like a charm.

  8. #28
    Join Date
    Feb 2010
    Location
    Brisbane, Australia
    Posts
    1
    Rep Power
    5

    Default

    Quote Originally Posted by FritzBrause View Post
    ... just checked with one server upgraded to 6.0.5: Blob compression enabled again an no issues with IMAP / Attachments so far. Everything is working like a charm.
    Agreed - everything is working smoothly again.

Similar Threads

  1. Clients stopped receiving emails
    By egadinc in forum Administrators
    Replies: 16
    Last Post: 12-14-2009, 03:38 PM
  2. [SOLVED] Sync problem with Yahoo! mail
    By ivan_de_miguel in forum Error Reports
    Replies: 1
    Last Post: 09-10-2009, 02:04 AM
  3. zmamavisdctl stopped and won't restart
    By alto in forum Installation
    Replies: 2
    Last Post: 04-18-2008, 01:41 AM
  4. [SOLVED] Upgraded to 5.0 OSS - Sendmail Problem
    By Chewie71 in forum Installation
    Replies: 11
    Last Post: 12-28-2007, 07:07 PM
  5. receiveing mail
    By maybethistime in forum Administrators
    Replies: 15
    Last Post: 12-09-2005, 04:55 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •