Hostname change not systemwide

Dark-Sider

Member
May 15, 2019
5
1
8
44
Hi folks,

thanks for this great looking appliance. I just installed the free version for some early testdrive - if it works out I'll be going for one of the subscriptions for my company.

Upon installation I typed in the wrong hostname (pmg.wrongdomain.com). I corrected my mistake in the webgui and also check that resolv.conf was updated properly. I then rebooted the machine.

The spam report mail (sent to the admin adress) now shows the following information:
sender: Proxmox Mail Gateway <postmaster@pmg.correctdomain.com>
subject: Proxmox Status Report - 2019-05-14 (pmg.wrongdomain.com)

The daily spam reports also link to pmg.wrongdomain.com. Have I missed a setting to update the domain name of the system?

On a side note. The status mail's To: is empty and the mail is sent as a BCC - is this intended? why?

regards,
Fabian
 
* Most likely you still have the old hostname configured in '/etc/hosts'
* the report should contain the same name you get when you run `hostname -f` in a shell

On a side note. The status mail's To: is empty and the mail is sent as a BCC - is this intended?
Yes this is intended - the rationale here is that we do not want to get NDR and Bounces back for this e-mail (since those would be again sent out to the admin e-mail) (technically the rationale is for the envelop sender, but adding a To header would only contain your e-mail address (or root@$fqdn))

Hope this helps!
 
* Most likely you still have the old hostname configured in '/etc/hosts'
* the report should contain the same name you get when you run `hostname -f` in a shell


Yes this is intended - the rationale here is that we do not want to get NDR and Bounces back for this e-mail (since those would be again sent out to the admin e-mail) (technically the rationale is for the envelop sender, but adding a To header would only contain your e-mail address (or root@$fqdn))

Hope this helps!

It would be great, if the GUI change will also change all necessary files. The problem has been already reported more often, primary on /etc/hosts kept unchanged.