==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2 from Github
- Deployed with iRedMail Easy or the downloadable installer? Download from Github
- Linux/BSD distribution name and version: FreeBSD 12.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL 12
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

# iRedMail Suggestions, Requests

## My setup

- FreeBSD 12.1 (soon 12.2, 13 next year)
- `openssl` instead of the defaults `libressl` (`libressl` does not have TLS 1.3 yet)
- Charset `en_AU.UTF-8` instead of `C`

## Suggestions

1. Create a question during the installation for `charset`, then do all-round configuration. I prefer to use `en_AU.UTF-8` instead of the default `C`.
    - FreeBSD

# Edit `/etc/login.conf`
    . . .
    default:\
            :charset=en_AU.UTF-8:\
            :lang=en_AU.UTF-8:\
            :setenv=LC_COLLATE=en_AU.UTF-8:\
    . . .
    root:\
            :charset=en_AU.UTF-8:\
            :lang=en_AU.UTF-8:\
            :setenv=LC_COLLATE=en_AU.UTF-8:\
    . . .
    postgres:\
            :charset=en_AU.UTF-8:\
            :lang=en_AU.UTF-8:\
            :setenv=LC_COLLATE=en_AU.UTF-8:\
            :tc=default:

# Update login db
cap_mkdb /etc/login.conf

# Edit `./iRedMail/conf/global`

    export LC_ALL=en_AU.UTF-8
    export LC_CTYPE=en_AU.UTF-8
    export LC_COLLATE=en_AU.UTF-8
    export LANG=en_AU.UTF-8

2. Update `perl 5.2` to `perl 5.3`

3. Is it `perl` used on anything else than replace strings, including `iredadmin`, `iredapd` and `mlmmjadmin`? If that is the case, could `iRedMail` use `sed` instead and avoid installing `perl`? I like installing the absolute minimum necessary for space and safety reasons. If it is a server, do not install what you do not need.

4. Skip installing docs. Unset build references to DEBUG, DOCS, EXAMPLES, MANPAGE, TEST (use `_UNSET`)
    - When used for production, there is no reason for documentation. Caution: Clam/Amavis need to catch issues in DOC files. Not the same kind of Doc.

5. `PHP 7.4` and `mcrypt` combo, both package and config (no longer necessary/available)

6. Update `Python 2` syntax (`except Exception, e:`). It is only two update files. ONly to keep the code clean.

find . -name "*.py" -print -exec grep ", e:" {} \;

sed -i '' -e "s/, e:/ as e:/" ./update/ldap/*.py

7. Configure compilers to minimum requirements such as disable cross-compile, etc. Some of the lengthy parts of the install are to compile all sorts of tools (dependency). Could those be installed using `pkg`?

8. Compile ahead supporting tools such as gmake, llvm, etc.

9. Curiosity: Why the install on FreeBSD compiles from the `ports` instead of using `pkg` binaries? I am guessing that this is historical to use the most recent code, and less for any specific flag. Having said that, I use `openssl` which is not the default on FreeBSD, so compilation is welcome.

Thanks
Stay safe.