+++ This bug was initially created as a clone of Bug #57512 +++ The emails generated by the self-service (maybe elsewhere, too) are rejected by Gmail's SMTP servers for lack of a proper `Message-Id` in their header: > Aug 13 12:14:03 postfix postfix/smtp[1252]: 4AB65C466981: to=<xxxx-value-removed-xxxx@gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.147.27]:25, delay=1.5, delays=0.35/0.34/0.29/0.52, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[142.250.147.27] said: 550-5.7.1 [194.76.91.97] Messages missing a valid Message-ID header are not 550-5.7.1 accepted. For more information, go to 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant and review 550 5.7.1 RFC 5322 specifications. a640c23a62f3a-a80f3fa7d31si92176566b.238 - gsmtp (in reply to end of DATA command)) It might be necessary to generate a message-id for outgoing messages, e.g. using a helper function from Python: https://docs.python.org/3/library/email.utils.html#email.utils.make_msgid This bug was reported by Johannes Bornhold on behalf of a customer.
cloned #57512 to be able to release the changes in 5.0errata and 5.2errata UCS 5.0 univention-self-service (5.0.11-3) 19e95a97cfa4 | Bug #57512: add Message-ID header to emails sent via Self Service univention-self-service.yaml e53793cc1343 | Bug #57953: add Message-ID header to emails sent via Self Service
<https://errata.software-univention.de/#/?erratum=5.0x1213>