Question about the RRT

Hello everybody,

I have a question regarding the RRT.

I have one user "e1421751-5ee1-4979-a3c4-84f0c5cc54cc@users.<my-domain>" and exactly one entry in my RRT:

[
  {"username":"mailer2","domain_name":"<my-domain>","target_address":"alias:e1421751-5ee1-4979-a3c4-84f0c5cc54cc@users.<my-domain>"}
]

There are no domain aliases, e.g. requests to the following endpoints of the webadmin API return empty lists:

/domains/<my-domain>/aliases
/domains/users.<my-domain>/aliases

When I request /users/e1421751-5ee1-4979-a3c4-84f0c5cc54cc@users.<my-domain>/allowedFromHeaders, I get the following result:

[
  "[email protected]",
  "mailer2@<my-domain>",
  "mailer2@users.<my-domain>"
]

Some more debugging:

Deleting the sole entry from the RRT removes the entries "mailer2@<my-domain>" and "mailer2@users.<my-domain>" from the allowedFromHeaders.
Adding another entry `{"username":"mailer2","domain_name":"users.<my-domain>","target_address":"alias:e1421751-5ee1-4979-a3c4-84f0c5cc54cc@users.<my-domain>"}` to the RRT does not change the allowedFromHeaders.
Adding another entry `{"username":"test","domain_name":"users.<my-domain>","target_address":"alias:e1421751-5ee1-4979-a3c4-84f0c5cc54cc@users.<my-domain>"}` to the RRT adds only the entry "test@users.<my-domain>" to the allowedFromHeaders.

So it seems like adding an alias with a different domain than the target to the RRT always creates two aliases: one with the user part and the domain of the alias and one with the user part and the domain of the target.
Why is this the case? Is it documented somewhere?

Best regards,
Felix


---
Gesellschaft für interkulturelles
Zusammenleben gGmbH (GIZ)
Felix Auringer
IT
Reformationsplatz 2
13597 Berlin

Tel: 030/513 0100 00; Fax: 030/513 0100 09 
www.giz.berlin; [email protected]

Amtsgericht Charlottenburg HRB 200872 B
Geschäftsführerin: Dr. Britta Marschke