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

Hi,

I just finished migrating my iRedMail server from FreeBSD to the dockerized version and I'm very impressed!  Great solution and works very well!  (I had been running on FreeBSD for about 2 years) 

The migration was much smoother than I expected and the docker container setup with the custom settings folder is much cleaner than all the settings and tweaks I had to track in FreeBSD.

Had a few questions about the docker image:

1.  When is the next update of the iredmail/mariadb:stable image?

https://hub.docker.com/r/iredmail/mariadb/tags

- The last update was ~3 months ago, and I saw that the postfix custom.sh bug (https://github.com/iredmail/dockerized/issues/76) has already been fixed, but it is not in the stable tagged image. 
- It'd be great to migrate from a customized main.cf file to this approach to be up-to-date.
- I did try the nightly image, but I found it was unstable with a problem related to clamav restarting constantly.

2.  When will SoGo be added to the docker image

- Is this on the plan?  I can submit a docker issue/request if needed.

3.  Need for a post container-startup custom "script" for remote logging -- and maybe other uses?

- I use a remote logging server, and need to send the postfix and dovecot logs to that server.  In docker files and docker-compose, you can send files to a remote log server, but it will only send whatever is in that containers' stdout or stderr.  The postfix and dovecot logs are not included in stdout or stderr so doesn't appear in the container logs.

- My temporary solution is to run a script on the docker host that redirects the log files after the container starts:

e.g. docker exec -d iredmail bash -c "tail -n 0 -q -F /var/log/maillog >> /proc/1/fd/1"

- If I could put the "tail -n 0 -q -F /var/log/maillog >> /proc/1/fd/1" into a custom.sh script inside the container, such as the way the postfix custom.sh script runs at startup, it would be much more reliable. 
- In my current approach, if the docker host restarts for some reason (power outage, etc), my script doesn't run.
- There may be other uses for a custom.sh startup script also for other users that need to make tweaks.

4.  iptables is not installed in the image, and is needed by fail2ban

- After install, I noticed several log errors from fail2ban.utils not working because iptables was not found.  This should probably be added to the container also. 
- I was able to install iptables after the container startup using the 'docker exec' process mentioned above in item 3, but that would not work on an automatic restart of the container so it should be installed by default.
- I can add this in github as a request if needed

Again, great product, and thank you!