Warning
THIS IS A DRAFT, DO NOT APPLY ANY STEPS MENTIONED IN THIS TUTORIAL.
Paid Remote Upgrade Support
We offer remote upgrade support if you don't want to get your hands dirty, check the details and contact us.
session.save_path
in php-fpm pool config file./etc/iredmail-release
with new iRedMail version numberiRedMail stores the release version in /etc/iredmail-release
after
installation, it's recommended to update this file after you upgraded iRedMail,
so that you can know which version of iRedMail you're running. For example:
0.9.7
Roundcube 1.2.4 fixes a security issue, all users are encouraged to upgrade it as soon as possible. For more details about this release, please check Roundcube release note.
Please follow Roundcube official tutorial to upgrade Roundcube webmail to the latest stable release immediately:
iRedMail-0.9.6 and earlier releases have an incorrect logrotate setting for Dovecot log file, it causes all Dovecot log files are empty due to no required permission to open log files. Please follow steps below to fix it.
Please open file /etc/logrotate.d/dovecot
, find line below:
create 0600 vmail vmail
Remove above line and save the change.
Attention
This is applicable to RHEL/CentOS system, and Nginx web server.
iRedMail-0.9.6 doesn't set path for session.save_path
parameter in php-fpm
pool config file /etc/php-fpm.d/www.conf
, please fix it with steps below:
/etc/php-fpm.d/www.conf
, find line:php_value[session.save_path] = "/var/lib/php/session"
sessions
(ends with s
), not session
. So
please change it to:php_value[session.save_path] = "/var/lib/php/sessions"
service php-fpm restart
Please open file /etc/fail2ban/filter.d/dovecot.iredmail.conf
, remove line
below:
\(no auth attempts in .* rip=<HOST>
Then restart or reload Fail2ban service.
Attention
This is not applicable to SOGo-2.x because it doesn't support backing up
all users' data with command sogo-tool backup /path/to/backup/dir ALL
.
iRedMail has script /var/vmail/backup/backup_mysql.sh
(or backup_pgsql.sh
)
to backup SOGo database by dumping whole database to a plain SQL file as
backup. It's not ideal because:
This new script does backup with sogo-tool backup
command to avoid issues
mentioned above, you can restore a single user's data or all users data with
sogo-tool restore
.
Please follow steps below to setup this daily cron job.
/var/vmail/backup
, if you prefer
a different directory, feel free to change the directory name used in commands
below:cd /var/vmail/backup/
wget https://bitbucket.org/zhb/iredmail/raw/default/iRedMail/tools/backup_sogo.sh
chmod +x backup_sogo.sh
/var/vmail/backup
like below
to store backup files:/var/vmail/backup
|- sogo/
|- 2017/ # <- year
|- 03/ # <- month
|- 22.tar.bz2 # <- day (file name is: <day>.tar.bz2)
If you prefer a different backup root directory, please open
`backup_sogo.sh`, update variable `BACKUP_ROOTDIR` with the new directory.
Open file backup_sogo.sh
, modify
Run command crontab -e -u root
to setup root user's cron job. Add content
below as new job:
# SOGo: backup all users' data at 3:05AM everyday.
5 3 * * * bash /var/vmail/backup/backup_sogo.sh
For more details about this backdooring mysqldump backup issue, please read blog post:
Steps to fix it:
Open the daily MySQL backup script, it's /var/vmail/backup/backup_mysql.sh
by default. if you use different storage directory during iRedMail
installation, you can find the base directory with command postconf virtual_mailbox_base
.
Find variable name CMD_MYSQLDUMP
like below:
export CMD_MYSQLDUMP="mysqldump ..."
--skip-comments
like below:export CMD_MYSQLDUMP="mysqldump ... --skip-comments"
For more details about this backdooring mysqldump backup issue, please read blog post:
Steps to fix it:
Open the daily MySQL backup script, it's /var/vmail/backup/backup_mysql.sh
by default. if you use different storage directory during iRedMail
installation, you can find the base directory with command postconf virtual_mailbox_base
.
Find variable name CMD_MYSQLDUMP
like below:
export CMD_MYSQLDUMP="mysqldump ..."
--skip-comments
like below:export CMD_MYSQLDUMP="mysqldump ... --skip-comments"