3 ms·
> It's in a docker image on my file server At this point you could|should run a proper mailsever with fetchmail. I'm running [0] specifically as a local archiv
by justsomehnguy 3y ago
> It's in a docker image on my file server
At this point you could|should run a proper mailsever with fetchmail. I'm running [0] specifically as a local archive solution. Now that can be accessed by Thunderbird.
docker.io/mailserver/docker-mailserver
- nfriedly 3y agoInteresting, I might try that. Your link seems to be broken, though - is this the right one? https://hub.docker.com/r/mailserver/docker-mailserver https://hub.docker.com/r/mailserver/docker-mailserver
- justsomehnguy 3y agoDuh, I just copied image name from the docker-compose.yaml *grin* But yeh, this one.
- Taywee 3y agoIt's not a link, it's the image name that you'd directly use from docker or podman. And yes, that's the same one. One of the things I found so confusing about docker at first was how much information you could leave out of your image reference and docker would assume the rest. I'd prefer if it only assumed localhost, and never automatically assumed any remote registry. There's really no reason for docker.io to be special.
- dingledork69 3y agoSomething else that's confusing is why these links don't just redirect to the registry landing page. A simple redirect from https://docker.io/mailserver/docker-mailserver https://docker.io/mailserver/docker-mailserver to https://hub.docker.com/r/mailserver/docker-mailserver https://hub.docker.com/r/mailserver/docker-mailserver would make so much sense.