
                    For dkim, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Hi There The Mailu-Project is currently in a bit of a bind! We are short on man-power 

Mailu Allow specific users to send email from any address

Mailu ClamAV using all my disk space

For my environment I put the log to syslog so in env:
LOG_DRIVER=journald
For the jail I've set blackhole route 

Mailu Access logfile for Fail2ban

It's not in the list of SASL mechanisms that are tried by default but starting with 2.0 you can use it manually: 

MailKit NTLM authentication not working in some cases

here my structure and the front docker-compose

 # Core services front: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}nginx:${MAILU_VERSION:-1.7} restart: always env_file: mailu.env logging: driver: json-file ports: # - 8080:80 # - 8443:443 - 10.28.201.155:25:25 - 10.28.201.155:465:465 - 10.28.201.155:587:587 - 10.28.201.155:110:110 - 10.28.201.155:995:995 - 10.28.201.155:143:143 - 10.28.201.155:993:993 volumes: - /data/mailu/letsencrypt/etc/letsencrypt/archive/domain.tld:/certs - /data/mailu/overrides/nginx:/overrides

Mailu Nginx Reverse Proxy error

Off topic but you once asked me which was more secure: OpenPGP vs S/MIME Well based on the Efail exploits released last week 