Why?
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
Your link seems to be broken, though - is this the right one? https://hub.docker.com/r/mailserver/docker-mailserver
But yeh, this 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.
A simple redirect from https://docker.io/mailserver/docker-mailserver to https://hub.docker.com/r/mailserver/docker-mailserver would make so much sense.
> I'm running it in a docker image on my file server, accessed via noVNC in a browser
That's interesting. I get a couple of newsletters with advertising in them, and while I still find the Thunderbird interface a little clunky, this might sway me a bit.
I'm currently running Thunderbird as an email backup solution, with a rule to automatically copy every new email to a local folder. Maybe I'll start using it a bit more. (It's in a docker image on my file server, accessed via noVNC in a browser, which definitely adds to the clunkiness. Maybe I'll switch it to my local machine.)