Univention Bugzilla – Bug 37649
mail/alias/root is not set up correctly during system setup
Last modified: 2021-05-03 21:27:30 CEST
Observed on DC slaves that has been set up via system setup (KVM generic template or EC2): mail/alias/root is not set up correctly during system setup. The domain part point still to the old domain name the system setup template has been installed with. In this case, the domain has been set to najjar.local during system setup but mail/alias/root still points to systemmail@ucs.local. So by default, mails to root resp. systemmail are lost, because postfix has (in nearly all cases) no idea where to send the mail to.
(In reply to Sönke Schwardt-Krummrich from comment #0) > In this case, the domain has been set to najjar.local during system setup > but mail/alias/root still points to systemmail@ucs.local. Correction: it points to systemmail@ucsmaster.ucs.local instead of systemmail@slave111.najjar.local
Small notes: - in EC2 mails to root/systemmail are lost because of this bug - this may also affect Univention Apps - in EC2 the old/wrong value for mail/alias/root is systemmail@unassigned-hostname.unassigned-domainname
IMHO the best solution for this would be to ask the user during the installation if she wants to supply an email address where all system related mails should ge to. I think most administrators would desire this. If no address is supplied, systemmail@ucsmaster.ucs.local should be used and a note/tooltip could inform the user how to read those emails (mail/mutt/etc, imo pine has the best beginner ux).
Happens in 4.1 with backup, slave and members in EC2. Breaks 01_base.110_ucr_cronjobs.test. mail/alias/root: systemmail@unassigned-hostname.unassigned-domain There is a workaround created for docker: ucs-4.1-0/mail/univention-mail-postfix/etc/univention/docker/init.d/50univention-mail-postfix that does set the UCRV.
*** Bug 31744 has been marked as a duplicate of this bug. ***
I observed this in our environment too, after installation and join of UCS, "mail/alias/root" still contains "systemmail@unassigned-hostname.unassigned-domain".
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
Still valid issue