Greetings,

While writing some automation that uses MySQL, I discovered the following:

Code:
[zimbra@mail2 ~]$ mysql  -e 'SELECT *  FROM zimbra.mailbox WHERE comment LIKE "user123%"\G'                                  *************************** 1. row ***************************
                id: 9389
          group_id: 89
        account_id: ec3328e5-fc42-4a5c-895a-813ec6b9643e
   index_volume_id: 2
item_id_checkpoint: 256
     contact_count: 0
   size_checkpoint: 0
 change_checkpoint: 1
     tracking_sync: 0
     tracking_imap: 0
    last_backup_at: NULL
           comment: user123@mycompany.com
  last_soap_access: 0
      new_messages: 0
idx_deferred_count: 0
   highest_indexed: 0
*************************** 2. row ***************************
                id: 10589
          group_id: 89
        account_id: 9d78151e-3f51-477c-9a87-6c994516a667
   index_volume_id: 2
item_id_checkpoint: 2768
     contact_count: 0
   size_checkpoint: 54854899
 change_checkpoint: 15318
     tracking_sync: 0
     tracking_imap: 0
    last_backup_at: NULL
           comment: user123@mycompany.com
  last_soap_access: 1369344588
      new_messages: 3
idx_deferred_count: 16
   highest_indexed: 15001-2701
While researching the issue I found this tidbit in a Wiki, "The comment field is mostly correct, but it is deemed unreliable since there are some corner cases where it can be duplicated." This in regard to constructing a query on the comment field as I did above.

Looking for some ideas on a safe way to remove the bogus account (id=9389). I would prefer to use the provisioning tool but don't see a way to specify criteria other than user name.

Any suggestions? Thanks!

Release 7.2.0_GA_2669.RHEL5_64_20120410001942 RHEL5_64 FOSS edition, Patch 7.2.0_P1.