mistermatt2u

There is discussion about this in issue #293. Basically you would do something like below: ``` $ docker-compose stop $ docker-compose rm $ docker pull maxking/mailman-core:$tag $ docker pull maxking/mailman-web:$tag...

@iot-resister Did you resolve this? I found a similar issue. I isolated it to the mailman database password that I had selected. The function in entrypoint.sh that parses the database...

@jlgarnier Those files need to be created as needed, I don't believe they are auto-created by the docker-compose or the container images. After the .4.0 series, my mailman-extra.cfg basically became...

@kordan Take a look at issue #412 and see if that might help. It seems like your chosen password might include any of /, ?, #, @, or :.

While reviewing the [urllib.parse documentation](https://docs.python.org/3/library/urllib.parse.html#module-urllib.parse), I found the excerpt below: **Characters in the netloc attribute that decompose under NFKC normalization (as used by the IDNA encoding) into any of /,...

@maxking I'll take this one as well, and will submit a PR.

+1, same thing here. Certificate was just issued today. Looking at the .p12 file in OpenSSL, the '-legacy' switch was required. Looking at the certificate after I finally got it...

I took a bit of a closer look at this. It seems the problem might be that the CA "Logbook of the World Root CA" is signed by itself. So...

Below is a script I placed in /etc/logrotate.d/mailman to address this issue. I believe this will rotate the logs every week, by default. You would need to confirm where your...