usually only the short name is set with hostname (`hostname mail`) - the fqdn is added to '/etc/hosts' pointing to an ip configured on the machine.
for PMG additionally the DNS-name is taken from the search list in '/etc/resolv.conf' - see
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_configuration_files_overview
Most things can be configured in the GUI (the search domain in this case for example). However I agree that two pieces are missing - setting the hostname and editing /etc/hosts - would you open an enhancement request over at
https://bugzilla.proxmox.com for this (product pmg, component pmg)
The one thing I currently don't see the point in making available over the GUI is the helo_name - since it is not necessary in most setups to set it differently from the hostname.
I hope this helps!
it makes totally sense! i'm hosting a bunch of domains for customers and now want to implement PMG (without re-doing my [split-horizon, internal/external] DNS-setup; let's say it's complex)
current setup is like (internet side):
domain-customer.xyz > mx=abc.domain-hoster.xyz
domain-hoster.xyz > mx=abc.domain-hoster.xyz
abc.domain-hoster.xyz = IP 100.100.100.100
current flow (simplified) of a sending eMail-Server:
want to send email for
user@domain-customer.xyz
– lookup of mx-record for domain-customer.xyz > result is "abc.domain-hoster.xyz"
– lookup of IP for abc.domain-hoster.xyz > result is "100.100.100.100"
– (maybe) doing reverse lookup of IP 100.100.100.100 and compare to result of mx lookup (maybe take actions if different)
– connecting to IP 100.100.100.100
– sending helo / receiving helo
– (maybe) verifying received helo <<< THIS now could ruin the delivery (my servers would stop here if it's not the same as the above lookups)
because i can't (and don't want to) change the internal DNS names/configuration of the systems, especially the mail server i need:
– a different DNS name for the PMG system (VM/CT) with a different IP
– so it's FQDN (and resulting hostname, etc.) are
different then abc.domain-hoster.xyz
– strictly configured/checking eMail-Server will see the mismatch between the send helo string of PMG (and the provided DNS informations)
–
BOOM, or maybe boom (depends)
my internal DNS names/IPs can't be changed in favor of PMG – it simply needs to send/respond to connections like the mail server itself.
THIS then guarantees, that the same setup (now with PMG in between) would work, without any modifications elsewhere (except maybe that the eMail-Server from then on sends it's outgoing eMails via PMG as smarthost, but not needed if not wanted); and in case of any intermitted problems it's easy as hell to temporarily remove PMG as well.
hopefully i could give reasons why we need this (little) change [for the better], which makes PMG an even more complete package for everyone.
NOBODY loses, but EVERYBODY wins!
