[SOLVED] pmgconfig sync parse error in /etc/pmg/transport
- Thread starter Kodey
- Start date
Not supported by pmg? I thought that this is a standard postfix/dovecot delivery mechanism.
Everything seems to be working with delivery. I don't understand the significance or implications of this error.
I assume the sync process didn't complete. What possible problems might I face?
Thank you for your response.
They're on the same host. Isn't that the most efficient delivery mechanism in this case?
I don't want to generate network traffic for no reason.
Also, if it's supported by postfix, how is it not regarded as correctly configured?
Dovecot is responsible for managing the virtual users mailboxes. It's not configured as a mail transport or open to the internet.
There are several options I've read about for this and probably more I haven't read about. My knowledge is probably a bit dated too.
What mechanism does pmg support/recommend for this? Is it documented anywhere?
generally it's not recommended to install too many other services on the same machine as pmg (it can work of course). the more suited way would be to seperate those things into their own vm/container/etc. and let them connect over the network.
if they run on the same machine (e.g. side by side, or different container on the same host) the "network" involved is really only copying in the memory, not much more than a local unix socket
i mean you can generally edit the postfix config by modifying the template (see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine) , but the remaining stack does not know about it then
if they run on the same machine (e.g. side by side, or different container on the same host) the "network" involved is really only copying in the memory, not much more than a local unix socket
because our software needs to parse the config file, since we want to make sure the user configures it correctly, but it also means that maybe not all options are supported that are in postfix
i mean you can generally edit the postfix config by modifying the template (see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine) , but the remaining stack does not know about it then
That definitely fixed it.
You might think this is "really only copying in the memory", but actually, it generates network traffic which can be snooped and logged even if they are side by side. That could be desirable in some cases, but seems like overkill.
I did consider installing Dovecot as a container, but Turnkey don't offer a Proxmox Dovecot image and I was a little surprised that an imap mailbox hosting service wasn't included in PMG, and I didn't see the sense using additional resources to provide a complete mail service. Besides, I have experience configuring these side by side so I just followed my nose.
It would be nice if this configuration was supported or even provided in PMG.
Thanks heaps for the help.
You might think this is "really only copying in the memory", but actually, it generates network traffic which can be snooped and logged even if they are side by side. That could be desirable in some cases, but seems like overkill.
I did consider installing Dovecot as a container, but Turnkey don't offer a Proxmox Dovecot image and I was a little surprised that an imap mailbox hosting service wasn't included in PMG, and I didn't see the sense using additional resources to provide a complete mail service. Besides, I have experience configuring these side by side so I just followed my nose.
It would be nice if this configuration was supported or even provided in PMG.
Thanks heaps for the help.