Zimbra Forums forum

Fantastic!! That's one mailbox sorted: Code: ls -lhtotal 2.5M-rw-rw----. 1 zimbra zimbra 2.3K Sep 30 23:02 appointment_dumpster.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:08 appointment_dumpster.ibd-rw-rw----. 1 zimbra zimbra 2.3K Sep 30 22:50 appointment.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:06 appointment.ibd-rw-rw----. 1 zimbra zimbra 2.4K Sep 30 23:10 data_source_item.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:10 data_source_item.ibd-rw-rw----. 1 zimbra zimbra 8.0K Sep 30 23:12 imap_folder.frm-rw-r-----. 1 zimbra zimbra 128K Sep 30 23:14 imap_folder.ibd-rw-rw----. 1 zimbra zimbra 1.6K Sep 30 23:16 imap_message.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:16 imap_message.ibd-rw-rw----. 1 zimbra zimbra 10K Sep 30 23:40 mail_item_dumpster.frm-rw-r-----. 1 zimbra zimbra 208K Sep 30 23:41 mail_item_dumpster.ibd-rw-rw----. 1 zimbra zimbra 11K Sep 30 23:38 mail_item.frm-rw-r-----. 1 zimbra zimbra 640K Sep 30 23:39 mail_item.ibd-rw-rw----. 1 zimbra zimbra 1.6K Sep 30 23:42 open_conversation.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:44 open_conversation.ibd-rw-rw----. 1 zimbra zimbra 2.4K Sep 30 23:47 pop3_message.frm-rw-r-----. 1 zimbra zimbra 112K Sep 30 23:48 pop3_message.ibd-rw-rw----. 1 zimbra zimbra 1.2K Sep 30 23:50 purged_conversations.frm-rw-r-----. 1 zimbra zimbra 96K Sep 30 23:50 purged_conversations.ibd-rw-rw----. 1 zimbra zimbra 2.7K Sep 30 23:52 purged_messages.frm-rw-r-----. 1 zimbra zimbra 96K Sep 30 23:53 purged_messages.ibd-rw-rw----. 1 zimbra

So far all seems to be going ok..... Sometimes I end up with a "cannot discard table due to foreign tag" error, but that can be disabled by: Code: SET FOREIGN_KEY_CHECKS=0;

I think I'm getting somewhere!!! Get the table structure from dbsake: Code: python3.9 /root/dbsake frmdump appointment.frm First connect to db: Code: MariaDB [(none)]> connect mboxgroup10; Then drop the table: Code: MariaDB [mboxgroup10]> drop table appointment; Move the ibd file out of the way: Code: $ mv appointment.ibd appointment.ibd.bak Create the table using the output of dbsake: Code: MariaDB [mboxgroup10]> CREATE TABLE `appointment` ( `mailbox_id` int(10) unsigned NOT NULL, `uid` varchar(255) NOT NULL, `item_id` int(10) unsigned NOT NULL, `start_time` datetime NOT NULL, `end_time` datetime DEFAULT NULL, PRIMARY KEY (`mailbox_id`,`uid`), UNIQUE KEY `i_item_id` (`mailbox_id`,`item_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Discard the tablespace: Code: MariaDB [mboxgroup10]> alter table appointment discard tablespace; Move the ibd file back: Code: $ mv appointment.ibd.bak appointment.ibd Import the original tablespace and check result: Code: MariaDB [mboxgroup10]> alter table appointment import tablespace;Query OK, 0 rows affected, 1 warning (0.01 sec)MariaDB [mboxgroup10]> select * from appointment;+------------+----------------------------------------------------+---------+---------------------+---------------------+| mailbox_id | uid | item_id | start_time | end_time |+------------+----------------------------------------------------+---------+---------------------+---------------------+| 10 | 91ad4a8d-46b5-455b-bd30-a8cf6795506a.1554815307104 | 22686 | 0000-00-08 30

Upgraded my Intalio FOSS install to 10.1.21 without problems. I will monitor.

The RPM's (even NE) are accessible in the public repo's: https://repo.zimbra.com/rpm/1010-ne/rhe ... x86_64.rpm

The significant CVEs affecting the FOSS version should be just these: CVE-2026-93641 CVE-2026-93647 Could someone with access to version 10.1.21 NE please post Share_all.js.zgz, MailCore_all.js.zgz, and NewWindow_2_all.js.zgz or zimbra-mbox-webclient-war-10.1.21.1789476131-1 here? Thanks.

Ok I think I'm getting somewhere?! I found something called `dbsake` which reads frm files as an alternative to the legacy `msyqlfrm` It seems to be working?? Code: python3.9 /root/dbsake frmdump appointment.frm---- Table structure for table `appointment`-- Created with MySQL Version 10.1.25--CREATE TABLE `appointment` ( `mailbox_id` int(10) unsigned NOT NULL, `uid` varchar(255) NOT NULL, `item_id` int(10) unsigned NOT NULL, `start_time` datetime NOT NULL, `end_time` datetime DEFAULT NULL, PRIMARY KEY (`mailbox_id`,`uid`), UNIQUE KEY `i_item_id` (`mailbox_id`,`item_id`)) ENGINE=InnoDB DEFAULT CHARSET=utf8; Maybe I can use the method written above now to hopefully restore the DB files

1. Here are some new cve for the 10.1.20 solved in the 10.1.21. Veille CVE — 3 entrée(s) nouvelle(s) ou modifiée(s) ====================================================================== CVE-2026-93641 [Zimbra] Score CVSS : 9.3 (CRITICAL) Publiée le : 2026-09-25 / modifiée le : 2026-09-25 An unauthenticated sender can forge a share notification that triggers stored XSS when a signed-in Zimbra Classic recipient clicks Accept Share, allowing the attacker to access mailbox data and act as the victim. https://nvd.nist.gov/vuln/detail/CVE-2026-93641 CVE-2026-93642 [Zimbra] Score CVSS : 9.3 (CRITICAL) Publiée le : 2026-09-25 / modifiée le : 2026-09-25 An unauthenticated sender can forge a share notification that triggers stored XSS when a signed-in Zimbra Modern recipient clicks Accept Share, allowing the attacker to access mailbox data and act as the victim. https://nvd.nist.gov/vuln/detail/CVE-2026-93642 CVE-2026-93647 [Zimbra] Score CVSS : 9.3 (CRITICAL) Publiée le : 2026-09-25 / modifiée le : 2026-09-26 An unauthenticated calendar sender can place active markup in a COUNTER message's RFC From address. Selecting the message in Zimbra Classic triggers stored XSS, allowing the attacker to access mailbox data and act as the victim. https://nvd.nist.gov/vuln/detail/CVE-2026-93647 When is-it planned to put out the 10.1.21 ? 2. I've to modify the postfix filters to block all the exploits mentioned in the cve(s) reports + some csp modifications. This tutorial also explains everything y

You can automatically fix the bug with : Code: cat > /etc/apt/apt.conf.d/99-zimbra-fixperms /dev/null | grep -q '^ii' && /opt/zimbra/libexec/zmfixperms || true";};EOF On debian/ubuntu Code: apt update & apt upgrade will call the fix over.

Good morning everyone, once again, following the release of version 10.1.21, these packages have appeared in the repositories (Rocky 9 with 10.1.20_GA_4200001.RHEL9_64_20260820122258 RHEL9_64 FOSS): yum update Dependencies resolved. ============================================================================================================= Package Architecture Version Repository Size ============================================================================================================= Upgrading: zimbra-core-components x86_64 10.1.8-1zimbra10.0b1.el9 zimbra-1010-oss 8.1 k zimbra-ldap-components x86_64 10.1.5-1zimbra10.0b1.el9 zimbra-1010-oss 7.3 k zimbra-nginx x86_64 1.24.0-1zimbra8.8b8.el9 zimbra-1010-oss 444 k zimbra-openjdk x86_64 17.0.19-1zimbra8.8b1.el9 zimbra-1010-oss 163 M zimbra-openjdk-cacerts x86_64 1.0.13-1zimbra8.7b1.el9 zimbra-1010-oss 136 k zimbra-proxy-components x86_64 1.0.16-1zimbra8.8b1.el9 zimbra-1010-oss 6.6 k I proceeded with the update, and this time, too, it is necessary to run the command: /opt/zimbra/libexec/zmfixperms -extended otherwise, the proxy service will not start after the restart of zimbra. Regards.

Thank you! Luckily I have access currently but it's good to have a "back door" so to speak if needed

It seems that the `mysqlfrm` command can't easily be installed on RH/CentOS etc... 8.x Scenario B: You have old .frm files (from MySQL 5.7 or older) that you need to read If you have legacy backup files and absolutely must use mysqlfrm to recover their structures, you cannot do it natively with the RHEL 8 repository version of MySQL 8. Instead, use one of these workarounds: • Option 1 (Easiest): Use Docker / Podman Run a temporary, legacy MySQL 5.7 container to parse the files or run the Python-based utility without messing up your host packages. • Option 2: Install via Python 2.7 (Manual) Because mysqlfrm is a legacy Python script, it requires Python 2.7 and the mysql-connector-python package. You would have to download the old mysql-utilities source code or RPM manually, as RHEL 8 defaults to Python 3. Without this command is there anyway at all to recover things? The current methodology that I posted in the previous link was something like this: Code: First, install MySQL Utilities. Then you can use mysqlfrm command in command prompt (cmd).Second, get the SQL queries from .frm files using mysqlfrm command:mysqlfrm --diagnostic /example_table.frmThen you can get the SQL query to create same structured table. Like this:CREATE TABLE `example_table` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(150) NOT NULL, `photo_url` varchar(150) NOT NULL, `password` varchar(600) NOT NULL, `active` smallint(6) NOT NULL, `plan` int(11) NOT NULL,PRIMARY KEY `PRIMARY` (`id`)) ENG