I created a rpm to install mailpiler in three docker containers managed by docker-compose, you will retrieve some documentation at : https://mailpiler.com/documentation/
each real user of the system can login (IMAP authentication), else
admin@local:pilerrocks
auditor@local:auditor
The backup is taking in to account
you have a piler wrapper to manage docker
[root@ns7loc11 ~]# piler
The commands are :
piler status : retrieve the status of piler container
piler bash : start a shell inside the container
piler restart: Restart the piler container
piler start: Start the piler container
piler stop: Stop the piler container
piler ps: Container information
piler log: Display the error log of the container
After a quick review, itâs a nice job. The imap authentication, and mail restore over imap indeed both work.
By setting the per domain bcc, postfix forwards emails to piler in the container.
A few polishing ideas:
set the antispam header in piler.conf in the spam_header_line variable. I can see nethserver uses rspamd. I assume it sets a specific mail header in case of a spam. By setting it in piler.conf, piler is able to indicate in the gui that itâs a spam message
âpiler statusâ canât find the health template for memcached and mysql
piler_piler_1 status
healthy
piler_mysql_1 status
Template parsing error: template: :1:8: executing ââ at <.State.Health.Status>: map has no entry for key âHealthâ
piler_memcached_1 status
Template parsing error: template: :1:8: executing ââ at <.State.Health.Status>: map has no entry for key âHealthâ
Iâll find some health checks for them, and let you know
when you fix the pilerâs vhost name with commands you mentioned then the $config[âSITE_URLâ] parameter changes accordingly in /etc/piler/config-site.php, however, $config[SITE_NAME_CONST] values doesnât change, it remains the default, ie. piler.domain.
Anyway, I think you did a great job so far. Perhaps one more question: how to handle piler version upgrades? Usually it would involve a new docker image, and once in a while a database schema fix, eg. adding a new table or similar.
need to check but in my VM I found piler unhealthy due to curl error, need to verify, thank
maybe a feature, I saw that piler does not like when the piler hostname was not defined in the /etc/hosts. something more to check
I thought to upgrade the docker-compose template we have in /etc/e-smith/templates/usr/share/piler/docker-compose.yml, so yes change the docker image accordingly of your upgrade, relative to the mysql upgrade we could start a script inside the mysql docker image like I did for the email importation. All of this could be done by a new nethserver-piler rpm version.
Thatâs not a good news
not aware, need to check how to host a docker repository on my server or elsewhere.
No, you did that right. I forgot to add both curl and support for the HELP command. Yesterday I fixed the image, so pull sutoj/piler:1.3.10 again, and it should be fine.
However, I couldnât get any meaningful health check possibility using the memcached container. It could be enhanced by adding a package like nc to do some periodic checks, but I think itâs much simpler to fix /usr/bin/piler script to use docker top to see if memcached is running, eg.
echo â# piler_memcached_1 statusâ
if [[ $(docker top piler_memcached_1 | grep -c memcached ) -eq 1 ]]; then echo âhealthyâ; else echo âunhealthyâ; fi
Also note that Iâve fixed the mariadb version to 10.5 in docker-compose.yaml
If thatâs the case, then itâs not necessary. However, I think thereâs a threshold to mark the message and spam (6.0 points), and another to deny it (20.0). Spam emails under 20.0 may be delivered to the archive.
But this can be a choice of the sysadmin, because they are in a range that it is not a spam because it is rejected immediately and it could be a false positive (good email with object renamed with SPAM and moved to junk).
one question, after I change the piler configuration in the volume piler_piler_etc/_data/piler.conf do you think piler needs to be restarted ? the documentation doesnât state on it