docker-mailserver: [BUG] bl.spamcop.net domain expired, resulting in rejected e-mails

Here’s a quick fix until this whole situation is resolved. To disable the spamcop check:

CONTAINER="your-container-name"
docker cp ${CONTAINER}:/etc/postfix/main.cf main.cf
# edit main.cf to comment out spamcop (in my case on line 47 and line 58)
docker cp main.cf ${CONTAINER}:/etc/postfix/main.cf
docker exec $CONTAINER postfix reload

I also tried overriding the hostname with

        extra_hosts:
            - "bl.spamcop.net:104.91.4.234"

in the compose file, but that didn’t work.

@williamdes there is information on https://hub.docker.com/r/tvial/docker-mailserver:

Migration / Deprecation Notice - We Migrated

We have migrated this repository to the Docker Mailserver Organization. This repository is therefore not maintained anymore. Please head over to the new repository for issues, pull requests and discussions. All work is now done there.

If someone uses tvial/docker-mailserver:latest I recommend to change image to: ghcr.io/docker-mailserver/docker-mailserver:latest due to fact that the docker hub needs some time to pull new images.

Or just use the actual new image mailserver/docker-mailserver.

EDIT: You have found it yourself now I guess 😃 Migration will take some time for all of the users, but had no other choice than to create this new image.

8.0.1 was just released and should be available in the next few minutes.

@williamdes there is information on https://hub.docker.com/r/tvial/docker-mailserver:

Migration / Deprecation Notice - We Migrated We have migrated this repository to the Docker Mailserver Organization. This repository is therefore not maintained anymore. Please head over to the new repository for issues, pull requests and discussions. All work is now done there.

This is the old master before I force-pushed the new master. Dockerhub seems to still resolve the old README, which is actually fine 😄

If someone uses tvial/docker-mailserver:latest I recommend to change image to: ghcr.io/docker-mailserver/docker-mailserver:latest due to fact that the docker hub needs some time to pull new images.

Why not just fast forward ?

I would say we need it just like a branch that anyone can follow

The rebase implicitly is a fast-forward 😃

@williamdes I updated the release description

💯 Perfect! You made me happy ^^

@williamdes I updated the release description

Detail I would ask to have:

• releases must have a changelog block
• GitHub releases should have an as detailed as possible description

@aendeavor (I have to look at commits and then the PR and then the issue to understand your release message) My point of view is: having a clear changelog and release message helps immediate updates to be made on production ENVs

@mrPjer thank you for your hotfix, saved me!

you have a small error in your command:

docker main.cf cp ${CONTAINER}:/etc/postfix/main.cf

cp and main.cf need to be switched, i think it would be a good idea to correct the post to have a working hotfix for all.