Merge branch 'iredmail:master' into fix-typo-sogo-update-1.7.1-1.7.2

Author: Kyshman

en_US/ee/0-ee.best.practice.md

@@ -303,11 +303,16 @@ Postfix doesn't support loading main settings (`/etc/postfix/main.cf` and
 `/etc/postfix/master.cf`) from multiple files, so iRedMail EE uses alternative
 solution to split core and custom settings.
 
-- The recommended way is using script `/opt/iredmail/custom/postfix/custom.sh`,
-  modifying settings in `main.cf` and `master.cf` with command `postconf -e`.
-  Details will be explained later in this section.
-- If you have many custom settings, you can maintain your own copy of `main.cf`
-  and `master.cf` under `/opt/iredmail/custom/postfix/` directory.
+- [Require EE v1.2.0] Write your new custom settings for `/etc/postfix/main.cf`
+  in file `/opt/iredmail/custom/postfix/append_main.cf`. EE will append all
+  content in this file to the end of `/etc/postfix/main.cf` each time you
+  perform upgrade, re-perform full deployment, or re-deploy Postfix.
+- [Require EE v1.2.0] Write your new custom settings for `/etc/postfix/master.cf`
+  in file `/opt/iredmail/custom/postfix/append_master.cf`. EE will append all
+  content in this file to the end of `/etc/postfix/master.cf` each time you
+  perform upgrade, re-perform full deployment, or re-deploy Postfix.
+- If you need to modify settings generated by EE, you can maintain your own
+  copy of `main.cf` and `master.cf` under `/opt/iredmail/custom/postfix/` directory.
     - If file `/opt/iredmail/custom/postfix/main.cf` exists, iRedMail EE will
       create `/etc/postfix/main.cf` as symbol link to this file.
     - If file `/opt/iredmail/custom/postfix/master.cf` exists, iRedMail EE
@@ -316,7 +321,7 @@ solution to split core and custom settings.
 For other settings, Postfix is configured to load files under
 `/opt/iredmail/custom/postfix/` first (they store custom settings and
 maintained by you), then another one from `/etc/postfix/` (maintained by
-iRedMail EE and you should __NOT__ modify them). If rule defined in first one
+iRedMail EE and you should __NOT__ modify them). If rule defined in custom files
 matches, Postfix will skip the second file.
 
 For example, Postfix is configured to load 2 files for HELO access check:
@@ -330,13 +335,13 @@ smtpd_helo_restrictions =
 ```
 
 - The first one, `/opt/iredmail/custom/postfix/helo_access.pcre`, is used to
-  store your cusotm HELO access rules. If rule in this file matched,
+  store your cusotm HELO access rules. If rule in this file matches,
   Postfix will ignore other rules defined later in same file, also the second
   file `/etc/postfix/helo_access.pcre`. So you can write rule in first file
   for new HELO access, or write same rule with different action to override the
   one defined in `/etc/postfix/helo_access.pcre`.
 - `/etc/postfix/helo_access.pcre`: This file is maintained by iRedMail EE,
-  please do NOT modify it.
+  do NOT modify it.
 
 You can find some other files for customization under
 `/opt/iredmail/custom/postfix/`. For example:
@@ -352,7 +357,7 @@ There's also a (Bash) shell scripting for flexible customization:
 deployment or upgrade.
 
 For example, to set value of parameter `enable_original_recipient` to `yes`
-(defaults to `no` set in `/etc/postfix/main.cf`), you can write  command in
+(defaults to `no` set in `/etc/postfix/main.cf`), you can write command in
 `/opt/iredmail/custom/postfix/custom.sh` like below:
 
 ```
@@ -387,6 +392,9 @@ It will generate new lines in `/etc/postfix/master.cf` like below:
 For more details about `postconf` command, please check its manual page:
 [postconf(1)](http://www.postfix.org/postconf.1.html).
 
+Updating configuration with `postconf` is not that user-friendly, use
+`append_main.cf` and `append_master.cf` if possible.
+
 ### Dovecot
 
 Dovecot supports loading from mulitple config files, and settings will be

en_US/ee/0-ee.changelog.md

@@ -6,6 +6,8 @@
 
 | Version | Release Date |
 |---|---|
+| [v1.2.1](#v1.2.1) | 2025-04-04 |
+| [v1.2.0](#v1.2.0) | 2025-04-03 |
 | [v1.1.0](#v1.1.0) | 2025-03-11 |
 | [v1.0.2](#v1.0.2) | 2025-02-20 |
 | [v1.0.1](#v1.0.1) | 2025-01-26 |
@@ -19,9 +21,71 @@
 
 <br/>
 
+- [iRedMail Enterprise Edition (EE)](https://www.iredmail.org/ee.html)
 - [Install iRedMail Enterprise Edition](./install.ee.html)
 - [Upgrade iRedMail Enterprise Edition](./upgrade.ee.html)
 
+## v1.2.1, Apr 4, 2025 {: #v1.2.1 }
+
+- Fixed issues:
+    - [SQL backends] Not apply required SQL changes to `vmail.mailbox` table.
+
+## v1.2.0, Apr 2, 2025 {: #v1.2.0 }
+
+- Breaking changes:
+    - Storing IMAP metadata in file inside mailboxes instead of SQL database.
+
+        If you have shared folders, or enabled http push notification, you
+        have to reset ACL or re-enable http push notification.
+
+- New features:
+    - [Z-Push](https://z-push.org) is now available as alternative ActiveSync server.
+        - Fail2ban integration for activesync auth failure is enabled by default.
+    - __Password recovery__. Allow end user to reset password with a recovery email. Notes:
+        - User must login to self-service and add recovery email first, so
+          that user can reset password with this recovery email.
+        - A SMTP Account is required to send emails while user requests to
+          reset password.
+
+- Improvements:
+    - [web] Add links to view per-domain, per-user mail activities.
+    - [web] Able to disable creating IMAP folder for email address extension.
+      When local user `user@domain.com` receives an email sent to
+      `user+ExT@domain.com`, do not create mailbox folder `ExT` and deliver
+      email to the folder.
+    - [web] Able to re-deploy backend database (MariaDB, PostgreSQL, OpenLDAP0.
+    - [server] Discard duplicate emails by default in global sieve rule.
+    - [server] Supports storing custom Postfix config snippets in
+      `/opt/iredmail/custom/postfix/append_main.cf` and `append_master.cf`.
+      Full content of these 2 files will be appended to the end of
+      `/etc/postfix/main.cf` and `master.cf`.
+    - [Fail2ban] Monitoring EE log file for login failures.
+    - [SOGo] Re-create SQL VIEW to display more contact info stored in
+      newly added SQL columns in `vmail.mailbox`.
+    - [SQL backends] Able to manage more info of a mail user: first name, last
+      name, mobile numbers, telphone numbers, birthday.
+
+- Fixed issues:
+    - [web] Updating `Server Settings` may lose some other settings.
+    - [web] Cannot re-upload custom logo image.
+    - [web] Typing 2FA security code doesn't work well with numeric keypad.
+    - [server] Incorrect firewall rules in some cases.
+    - [server] Incorrect sql column in SQL VIEW `sogo.users`.
+    - [server] Storing IMAP metadata in SQL is not working well, fallback to
+      store in file inside user mailbox instead.
+    - [server] Not sync mail attachment size with web upload file size.
+    - [server] Incorrect SQL column definitions in table `amavisd.msgs`.
+    - [server] Error while setting owner/permission of a lot DKIM keys.
+      Thanks subarticThrone@forum for the feedback.
+
+- Updated translations:
+    - de_DE (German). Thanks to Jochen Häberle <jh _at_ networkerz.de>.
+
+- Updated packages:
+    - adminer v5.1.1
+    - iRedAPD 5.9.0
+    - netdata 2.3.2
+
 ## v1.1.0, Mar 11, 2025 {: #v1.1.0 }
 
 - API:

en_US/ee/0-ee.translation.md

@@ -0,0 +1,35 @@
+# Translate EE to your local language
+
+[TOC]
+
+## Download language files
+
+You can download EE language files after login as global admin:
+
+1. Click the language icon on top-left page
+2. Click the small cloud icon to download all translation files in a zip package.
+
+![](./images/ee/download-translations.png){: width=600px }
+
+## How to translate:
+
+* Unzip the downloaded zip file.
+* Copy `en_US.json` to a new file named in your local language code. e.g. `de_DE.json`.
+* Translate the copied `de_DE.json` file.
+
+## How to test your translation
+
+- Upload translated JSON file to directory `/opt/iredmail/conf/locales/` on iRedMail server.
+- Make sure it's owned by correct user/group, then restart `iredmail` service to load it:
+
+```shell
+chown iredweb:iredweb /opt/iredmail/conf/locales/*.json
+chmod 0555 /opt/iredmail/conf/locales/*.json
+systemctl restart iredmail
+```
+
+- Login to EE web ui as global admin, domain admin, and end user, check around
+  and verify your translation.
+
+Do not forget to send your translation to [iRedMail team](https://www.iredmail.org/contact.html),
+so that others can benefit from it. :)

en_US/ee/_title.md

@@ -3,6 +3,7 @@ __iRedMail Enterprise Edition (EE)__ {: #ee }
 - [Install iRedMail Enterprise Edition](./install.ee.html)
 - [Best Practice](./ee.best.practice.html)
 - [ChangeLog](./ee.changelog.html)
+- [Translate EE to your local language](./ee.translation.html)
 - [Request a free cert from Let's Encrypt](./letsencrypt-ee.html)
 - Migration:
     - [Migrate from iRedMail Easy](./easy.to.ee.html)

en_US/faq/1-errors.md

@@ -323,3 +323,25 @@ Notes:
   a testing server, you can follow
   [our tutorial](./completely.disable.amavisd.clamav.spamassassin.html) to
   disable some features of Amavisd to keep it running, or disable it completely.
+
+## SOGo Groupware
+
+### No child available to handle incoming request
+
+Sample log lines:
+
+> Jul 02 00:41:15 sogod [2156]: [ERROR] <0x0x555dee9f6a20[WOWatchDog]> _No child available to handle incoming request!_
+
+If means SOGo doesn't have enough child processes to handle new requests.
+Please increase the processes defined in `PREFORK=` line in
+
+- RedHat-family OS: `/etc/sysconfig/sogo`
+- Debian / Ubuntu: `/etc/default/sogo`
+
+On FreeBSD and OpenBSD, please increase the value of `WOWorkersCount` parameter
+in SOGo config file instead:
+
+- FreeBSD: `/usr/local/etc/sogo/sogo.conf`
+- OpenBSD: `/etc/sogo/sogo.conf`
+
+Restarting SOGo service is required after you made this change.

en_US/faq/backup.restore.md

@@ -295,6 +295,11 @@ except `/var/lib/ldap/iredmail.org/DB_CONFIG`.
 # slapadd -f /etc/openldap/slapd.conf -l /var/vmail/backup/ldap/2015/05/2015-05-10-03:01:01.ldif
 ```
 
+    You may see a message like `The first database does not allow slapadd;
+    using the first available one (2)`, it's safe to ignore it since the
+    first one is database `monitor` which is created and maintained by
+    OpenLDAP internally.
+
 * It's OK to start OpenLDAP server now. It may report errors like below:
 
 ```

en_US/howto/webmail.customization.md

@@ -31,9 +31,37 @@ $config['skin_logo'] = '...';   // Please read the comment lines in
 ### Logo image
 
 You can set custom logo image displayed on the login page of SOGo by replacing
-file `sogo-full.svg`:
+file `sogo-full.svg`, but it will be overridden each time you upgrade SOGo
+packages:
 
 * On RHEL/CentOS: `/usr/lib64/GNUstep/SOGo/WebServerResources/img/sogo-full.svg`
 * On Debian/Ubuntu, it's `/usr/lib/GNUstep/SOGo/WebServerResources/img/sogo-full.svg`
 * On FreeBSD, it's `/usr/local/GNUstep/Local/Library/SOGo/WebServerResources/img/sogo-full.svg`.
 * On OpenBSD, it's `/usr/local/lib/GNUstep/SOGo/WebServerResources/img/sogo-full.svg`.
+
+Another way to customize Nginx config file to handle http request to this
+logo image.
+
+Edit file `/etc/nginx/templates/sogo.tmpl`, add these lines at the beginning:
+
+```
+location = /SOGo.woa/WebServerResources/img/sogo-full.svg {
+    return 301 https://myhost.com/sogo-full.svg;
+}
+```
+
+You can even use different logo images for each web domain:
+
+```
+location = /SOGo.woa/WebServerResources/img/sogo-full.svg {
+    if ($host = "domain1.com") {
+        return 301 https://myhost.com/sogo-full-domain1.com.svg;
+    }
+
+    if ($host = "domain2.com") {
+        return 301 https://myhost.com/sogo-full-domain2.com.svg;
+    }
+
+    return 404;
+}
+```

en_US/iredmail-easy/4-iredmail-easy.release.notes.md

@@ -10,6 +10,27 @@
 
 [TOC]
 
+## Version: 2025040201 (Apr 2, 2025) {: id=2025040201 }
+
+- Improvements:
+    - Amavisd: Create symbol link `/etc/amavisd.conf` on RHEL-family.
+    - dovecot: Switch to old stats plugin so that netdata can collect metrics.
+    - netdata: Switch all Python plugins to Go for better performance.
+    - netdata: Avoid the login page and splash screen, also disable cloud.
+
+- Fixed issues:
+    - SOGo doesn't have correct GroupObjectClasses setting for OpenLDAP backend.
+    - Netdata doesn't collect data for OpenLDAP server.
+    - Amavisd requires at least 2 child processes (was set to 1).
+    - Amavisd cannot save mail subject longer than 255 characters.
+
+* Updated packages:
+    - adminer v5.1.1
+    - mlmmjadmin 3.3.1
+    - netdata v2.3.2
+    - roundcube 1.6.10
+    - iRedAPD 5.9.0
+
 ## Version: 2025012401 (Jan 24, 2025) {: id=2025012401 }
 
 - Improvements:
@@ -20,7 +41,7 @@
     - Don't use deprecated LDAP attributes: storageBaseDirectory,
       mailMessageStore.
     - Disable SpamAssassin rule `RCVD_IN_DNSWL_HI` (Sender listed at
-      http://www.dnswl.org/, high trust).
+      http://www.dnswl.org/, high trust) due to too many false positivies.
 
 - Fixed issues:
     - Not serve ACME challenge over HTTP directly.

en_US/upgrade/0-migrate.or.upgrade.iredadmin.md

@@ -29,6 +29,8 @@ either open source edition or iRedAdmin-Pro).
    so you __MUST__ upgrade iRedMail to the latest stable release before
    upgrading iRedAdmin-Pro.
 
+    * [iRedMail Upgrade Tutorials](./iredmail.releases.html)
+
     * If you run the latest iRedAdmin-Pro with old iRedMail release, you may
       get error due to missing some required ldap attribute/value pairs
       (OpenLDAP backend), or missing some required SQL columns.

en_US/upgrade/0-upgrade.iredmail.1.7.2-1.7.3.md

@@ -12,7 +12,8 @@
 
 ## ChangeLog
 
-- XXX XX, 2025: initial publish.
+- Apr 10, 2025: fix incorrect ldap schema file.
+- Apr 4, 2025: initial publish.
 
 ## General (All backends should apply these changes)
 
@@ -56,7 +57,7 @@ Please follow below tutorial to upgrade mlmmjadmin to the latest stable release:
 
 * [Upgrade Roundcube](https://github.com/roundcube/roundcubemail/wiki/Upgrade).
 
-### Upgrade netdata to the latest stable release (v2.3.0)
+### Upgrade netdata to the latest stable release (v2.3.2)
 
 If you have netdata installed, you can upgrade it by following this tutorial:
 [Upgrade netdata](./upgrade.netdata.html).
@@ -65,9 +66,7 @@ If you have netdata installed, you can upgrade it by following this tutorial:
 
 ### Update LDAP schema file
 
-New schema allows mail user account to use 2 more attributes:
-- `recoveryEmail`,
-- `birthday`.
+New schema allows mail user account to use 2 more attributes: `recoveryEmail`, `birthday`.
 
 Download the latest iRedMail LDAP schema file:
 

en_US/upgrade/1-iredmail.releases.md

@@ -38,6 +38,7 @@
 
 Release Notes | Date | Upgrade tutorial | Comment
 ---|---|---|---
+[1.7.3](https://forum.iredmail.org/topic20846.html) | Apr 4, 2025 | [Upgrade from iRedMail-1.7.2](./upgrade.iredmail.1.7.2-1.7.3.html) |LDAP schema change.|
 [1.7.2](https://forum.iredmail.org/topic20760.html) | Jan 24, 2025 | [Upgrade from iRedMail-1.7.1](./upgrade.iredmail.1.7.1-1.7.2.html) |LDAP schema change.|
 [1.7.1](https://forum.iredmail.org/topic20547.html) | Aug 5, 2024 | [Upgrade from iRedMail-1.7.0](./upgrade.iredmail.1.7.0-1.7.1.html) ||
 [1.7.0](https://forum.iredmail.org/topic20501.html) | Jul 17, 2024 | [Upgrade from iRedMail-1.6.8](./upgrade.iredmail.1.6.8-1.7.0.html) ||

html/backup.restore.html

@@ -310,6 +310,11 @@ <h4 id="how-to-restore-openldap-backup">How to restore OpenLDAP backup</h4>
 </ul>
 <pre><code># slapadd -f /etc/openldap/slapd.conf -l /var/vmail/backup/ldap/2015/05/2015-05-10-03:01:01.ldif
 </code></pre>
+<pre><code>You may see a message like `The first database does not allow slapadd;
+using the first available one (2)`, it's safe to ignore it since the
+first one is database `monitor` which is created and maintained by
+OpenLDAP internally.
+</code></pre>
 <ul>
 <li>It's OK to start OpenLDAP server now. It may report errors like below:</li>
 </ul>