Zimbra Forums

I just saw the notification on the email newsletter of the latest blog announcement today. I hadn't noticed the announcement in early April. Zimbra 9.0.0 End of General Support: 03/31/2024 Zimbra 8.8.15 End of General Support: 12/31/2023 7 months is what you give us? I have been setting up Zimbra se...

#!/bin/sh for account in `zmprov -l gaa`; do forwardingaddress=`zmprov ga $account |grep 'zimbraPrefMailForwardingAddress' |sed 's/zimbraPrefMailForwardingAddress: //'` if [ "$forwardingaddress" != "" ]; then echo "$account is forwarded to $forwardingaddress" else forw...

We have had a couple of cases in the last few days of an account getting hacked and someone sending thousands of spam messages. We assumed these accounts were phished. After looking at the access logs, I found that the source attacker address had also showed up in the /opt/zimbra/log/access_log.2023...

We have had a couple of cases in the last few days of an account getting hacked and someone sending thousands of spam messages. We assumed these accounts were phished. After looking at the access logs, I found that the source attacker address had also showed up in the /opt/zimbra/log/access_log.2023...

Thanks for this. I had to import a single .PST mailbox of an ex-staff member that we had archived off of our Zimbra server for long term safe keeping. The import tool on the Zimbra website is called ZimbraMigration_8.8.15.1834_x64 and the instructions on the wiki say to use port 7071, which is the a...

I thought I had this issue fixed in November, but I got it again on February 1, 2022. The crontab job emails that come through just show that the certificate is not yet expired. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mail.m...

sbourdette wrote:Creating the tmp directory while the upgrade solve the issue

regards

Can you elaborate on which tmp dircectory you created and what the exact path was? Please elaborate since this is happening to quite a few of us.

Thanks,
David

:D I followed this guide and I now have a fully working zimbra with up to date certificates. Replace with your domain :) Then: cp /etc/letsencrypt/live//privkey.pem /opt/zimbra/ssl/zimbra/commercial/commercial.key chown zimbra:zimbra /opt/zimbra/ssl/zimbra/commercial/commercial.key wget -O /tmp/ISR...

I've been seeing this a bit after patching 8.8.15 and it is fixed after a complete server reboot.

Not just a zimcontrol restart.

Commenting here for anyone that sees this error after a recent patch upgrade, and to remind myself.

I'm also seeing this when applying the latest patches on the following:

Ubuntu 18.04.6 LTS
Release 8.8.15.GA.3829.UBUNTU14.64 UBUNTU18_64 FOSS edition, Patch 8.8.15_P27

I also saw it with the previous patch a couple of months ago.