@simos Thanks for your interest in this problem.
Yes MIAB is an interesting project for those of us who are not too technical but who wish to control their own mailserver. I ran it for about two years on another VPS and it worked well but the VPS provider closed down which is why I need to set it up now.
I have set up LXD proxy devices for another container which has the nginx reverse proxy which is handling port 80 and 443 proxies to the mail server.
I have set up LXD Reverse Proxies for the mail server container for ports 25, 143, 993, 465, 587 and 4190. (You said to me in a previous post that it would be better to forward these through the nginx reverse proxy too but I haven’t worked out how to do the nginx conf file to achieve this yet.) I have used “proxy_protocol=true” addition to the command to establish these ports.
The mail server is running and I am able to send emails from it but it is not receiving emails as yet. There are 2 or 3 other configuration errors reported by the mailserver with a couple of dns A records that are needed on my nameserver provider. These are for entries concerned with autoconfig.mydomainname and
I have set up the A records on the nameserver but my mailserver is reporting that the domain currently resolves to [Not Set] in public DNS. I suspect this is as a result of the DNS error reported by the status check that is the subject of this thread.
Thanks again for your help.