<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>After some further checking, I have learned that this repo key issue apparently affects all Ubuntu 20.04 and 22.04 installs for both Zimbra 10.0 and 10.1. I did not have a 9.0 install available to check, however I think we can reasonably presume it would affect it too, and probably 8.8.15 as well.</div><div><br data-mce-bogus="1"></div><div>In digging around some more, I noticed that the new Zimbra repo key I installed today seems to have a sub-key now associated with it that it did not have before. I am thinking the Zimbra development team made an unannounced change to their repos where they are now signing packages with this newer sub-key rather than the main key they were using earlier.</div><div><br data-mce-bogus="1"></div><div>So to recap, if you have Zimbra installed on Ubuntu 20.04 or 22.04, here is how to fix the issue and obtain Zimbra's new repo sub-key:</div><div><br data-mce-bogus="1"></div><div>Delete the repo key:</div><div>sudo apt-key del 254F9170B966D193D6BAD300D5CEF8BF9BE6ED79<br><br>Copy the key import script from: <a href="https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Adding_the_Zimbra_Repository_key">https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Adding_the_Zimbra_Repository_key </a>and run it with:</div><div><br data-mce-bogus="1"></div><div>sudo chmod +x zimbra_gpg.sh<br>sudo ./zimbra_gpg.sh<br></div><div><br data-mce-bogus="1"></div><div>Update your local host's repo cache:</div><div>sudo apt update</div><div><br data-mce-bogus="1"></div><div data-marker="__SIG_PRE__"><div><div><div><span style="color:rgb( 255 , 102 , 0 );font-weight:bold"><br>Randy Leiker (</span><span style="font-weight:bold"> <span style="color:rgb( 51 , 51 , 255 );background-color:rgb( 255 , 255 , 255 )">randy@skywaynetworks.com</span> <span style="color:rgb( 255 , 102 , 0 )">)</span></span><br><span style="color:rgb( 0 , 0 , 153 )">Skyway Networks, LLC</span><br><span style="color:rgb( 0 , 0 , 153 )"></span></div><div><span style="color:rgb( 0 , 0 , 153 )"><br data-mce-bogus="1"></span></div></div></div></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Randy Leiker" <randy@skywaynetworks.com><br><b>To: </b>"users" <users@lists.zetalliance.org><br><b>Sent: </b>Thursday, March 20, 2025 12:35:54 PM<br><b>Subject: </b>Zimbra repo key issue & solution for Ubuntu<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:12pt;color:#000000"><div>Hi Everyone,</div><br><div>I noticed on all of the Ubuntu 20.04 servers with Zimbra installed that I maintain that running "sudo apt update" recently began returning warnings like these:</div><br><div>Err:1 https://repo.zimbra.com/apt/onlyoffice focal InRelease<br> The following signatures were invalid: EXPKEYSIG 5234D2B73B6996C7 Zimbra Packaging Services <packaging-devel@zimbra.com><br>Err:2 https://repo.zimbra.com/apt/87 focal InRelease<br> The following signatures were invalid: EXPKEYSIG 5234D2B73B6996C7 Zimbra Packaging Services <packaging-devel@zimbra.com><br>Err:3 https://repo.zimbra.com/apt/1000 focal InRelease<br> The following signatures were invalid: EXPKEYSIG 5234D2B73B6996C7 Zimbra Packaging Services <packaging-devel@zimbra.com><br>Err:4 https://repo.zimbra.com/apt/1000-ne focal InRelease<br> The following signatures were invalid: EXPKEYSIG 5234D2B73B6996C7 Zimbra Packaging Services <packaging-devel@zimbra.com><br><br></div><div>In checking the Zimbra repo key with "sudo apt-key list" and it does not appear the key expired, so it is not clear to me what happened to it:</div><br><div>/etc/apt/trusted.gpg<br>--------------------------<br>pub rsa4096 2015-03-19 [SC]<br> 254F 9170 B966 D193 D6BA D300 D5CE F8BF 9BE6 ED79<br>uid [ unknown] Zimbra Packaging Services <packaging-devel@zimbra.com><br>sub rsa4096 2015-03-19 [E]<br><br></div><div>Here is how I fixed it:</div><br><div>sudo apt-key del 254F9170B966D193D6BAD300D5CEF8BF9BE6ED79</div><br><div>Copy the key import script from: <a href="https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Adding_the_Zimbra_Repository_key" target="_blank" rel="nofollow noopener noreferrer">https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Adding_the_Zimbra_Repository_key</a> and run it:</div><br><div>sudo ./zimbra_gpg.sh</div><div>sudo apt update</div><br><div>And all works correctly again:</div><br><div>Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease<br>Hit:2 https://repo.zimbra.com/apt/87 focal InRelease<br>Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease<br>Hit:4 https://repo.zimbra.com/apt/1000 focal InRelease<br>Hit:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease<br>Hit:6 http://us.archive.ubuntu.com/ubuntu focal-security InRelease<br>Hit:7 https://repo.zimbra.com/apt/1000-ne focal InRelease<br>Reading package lists... Done<br>Building dependency tree<br>Reading state information... Done<br>All packages are up to date.</div><br><div><div><div><div><span style="color:rgb( 255 , 102 , 0 );font-weight:bold"><br>Randy Leiker (</span><span style="font-weight:bold"> <span style="color:rgb( 51 , 51 , 255 );background-color:rgb( 255 , 255 , 255 )">randy@skywaynetworks.com</span> <span style="color:rgb( 255 , 102 , 0 )">)</span></span><br><span style="color:rgb( 0 , 0 , 153 )">Skyway Networks, LLC</span></div></div></div></div></div><br></div></div></body></html>