Introduce domain, address, and alias management #7
Labels
No labels
Security
TeX
auto-update
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Postbuero#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
changed title from Introduce {-e-}mai{-l-} address management to Introduce {+do+}mai{+n,+} address{+, and alias+} management
mentioned in issue #8
Thoughts:
Add settings for global domains for Person and Group (e.g.
users.aleksis.exampleandgroups.aleksis.example. Then, aliases are automatically resolved in a generic way with username/short_name as local part.Things like
group_short_name-role_shortname@are possible for e.g. reaching the owners of a group.MailAliasForGroupandMailAliasForPersonare then only used for cases not matching the general schema.