-
Notifications
You must be signed in to change notification settings - Fork 2
Description
See https://community.galae.net/ui/workspaces/1/contents/thread/2979 (FR)
Situation
Currently
- galae allows automatic
+aliases in both reception and sending:- you can send from
user@domain.tlnaccount using a from address likeuser+someresource@domain.tld - you can receive to
user@domain.tlnaccount emails sent touser+someresource@domain.tld
- you can send from
- galae allows automatic
.*wildcard aliases in reception:- you can receive to
user@domain.tldaccount emails sent tosomeadresse.anyresource@domain.tld(you need to define a wildcard alias on domain)
- you can receive to
- you cannot send as
someadresse.anyresource@domain.tld
Expected
Being able to send as a random (wildcard matching) address.
Workaround
Allow user to send for the entire domain. In this case, the from address is not checked. Unfortunately, this is a domain-wide parameter, so all users would be able to send for anybody.
Difficulties
A consistent behavior would be to allow the recipient of a wildcard to send « as the wildcard »
Example:
Imagine I setup a wildcard project*@domain.tld which redirect messages to team@domain.tld. This is a domain level configuration
All emails sent to projectX@domain.tld or projectY@domain.tld will be redirect to team@domain.tld mailbox. That would be nice to be able to send as projectX@domain.tld when loggedin as team@domain.tld.
Unfortunately, in the wildcard alias definition, there is no explicit relation between the team@domain.tln account and the alias address itself. Even more, team@domain.tln may be an alias to a series of mailboxes or a remote email address like recipient@anotherdomain.tld.
Because of this, this would be quite difficult to setup send authorization for user account that match the alias recipient address.