Results 1 to 5 of 5

Thread: 5.0.13 Released/5.0.12 Bug

Hybrid View

  1. #1
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Exclamation 5.0.13 Released/5.0.12 Bug

    A severe regression was introduced in 5.0.12, which allows an admin to add an existing account or distribution list (item 1) as an alias for other accounts or lists (item 2) which results in the deletion of the first item's LDAP entry.

    New binaries will be up later this week as 5.0.13

    How to avoid the issue if on 5.0.12: Search for any current accounts matching the desired address before adding an alias.

    If you've hit this issue see comment #5 on the bug for recovery steps (restore from LDAP backup, or remove the alias then create a new account with the exact same zimbraId of the one accidentally deleted, as mailbox data should still be intact).

    Bug 35100 - Able to add active account to other users alias lists


    ---

    Further technical details:

    As it's a missing check in LDAP provisioning code, it will happen regardless of the management type you employ; affects admin console/LDAP/JAVA/SOAP/CLI methods. The correct behavior is for the server to respond with an error that the name is already in use.

    Normally when you try to add an alias, if the LDAP entry already exists, it checks if the alias is 'dangling' (pointing to a non-existing target). If it is free, then it cleans up the address and then creates a new alias entry in LDAP. The bug misses checking if the entry is really an alias when deleting a dangling alias - thereby classifying it as free and modifying the LDAP entry for the first account. All email for account A will point at account B, and A is effectively gone from the system.

    In other words: Attempting to add an alias that's actually an existing account will convert the existing account entry in LDAP into an alias entry.
    Last edited by mmorse; 02-05-2009 at 01:49 PM.

  2. #2
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    The bits are now available - our apologies for the inconvenience.

    5.0.13 Network Edition: Release Notes & Downloads

    5.0.13 Open Source Edition: Release Notes & Downloads


    Edit:
    Though it's less of a concern if you've been using the fixed zmlogswatchctl script from Bug 33604 – Server Status Error it doesn't hurt to check for stray logger instances before upgrading.

    zmcontrol stop
    ps aux | grep logger
    kill -9 pid#

    5.0.14 will contain Bug 35002 – upgrade script should kill all zmlogger processes after zmloggerctl stop & Bug 26281 – Check Logger DB integrity and Connection Prior to Installing
    Last edited by mmorse; 02-12-2009 at 01:25 PM.

  3. #3
    Join Date
    Aug 2007
    Location
    Czech Republic
    Posts
    13
    Rep Power
    8

    Default

    Downloads: Page not found :-(

  4. #4
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    URLs have been updated.

  5. #5
    Join Date
    Aug 2007
    Location
    Czech Republic
    Posts
    13
    Rep Power
    8

    Default Thank You!

    Thank You! :-)

Similar Threads

  1. Bug 31450 followup
    By ezu in forum General Questions
    Replies: 37
    Last Post: 03-04-2009, 09:46 PM
  2. 5.0.6 is out!
    By mmorse in forum Announcements
    Replies: 0
    Last Post: 05-23-2008, 01:16 PM
  3. 5.0.4 is live!
    By mmorse in forum Announcements
    Replies: 0
    Last Post: 03-24-2008, 03:27 PM
  4. 5.0.3/.4 is out!!!
    By mmorse in forum Announcements
    Replies: 0
    Last Post: 03-20-2008, 04:20 PM
  5. serious IMAP download bug (6326)
    By ericding in forum Developers
    Replies: 5
    Last Post: 04-05-2006, 10:34 AM

Posting Permissions

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