[bug]: Mailing list cannot be created: Invalid principal name

[ghz7l]

What happened?

On version v0.10.7, when creating a new mailing-list, the system complains that "Principal name must include a valid domain assigned to the tenant."

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

1. Go to Directory > Lists
2. Create a new list:
3. Entre "Example" for list name;
4. Enter Tenant X for domain example.org;
5. Enter foo@example.org for Email;
6. Save and watch it fail.

Adding members or external members does not affect the error.

Version

v0.10.x

What database are you using?

RocksDB

What blob storage are you using?

RocksDB

Where is your directory located?

Internal

What operating system are you using?

Linux

Relevant log output

Notes:

1. Replaced IPv6 with "IPv6", secret with "SECRET", tenant with "TENANT", and Domain name with "example.org"
2. Nginx frontend is configured with proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

2024-12-12T17:49:43Z WARN X-Forwarded-For header is missing (http.x-forwarded-missing) listenerId = "https", localPort = 443, remoteIp = IPv6, remotePort = 39914
2024-12-12T17:49:43Z TRACE Expression evaluation result (eval.result) listenerId = "https", localPort = 443, remoteIp = IPv6, remotePort = 39914, id = "server.http.allowed-endpoint", result = "Integer(200)"
2024-12-12T17:49:43Z TRACE Write batch operation (store.data-write) elapsed = 0ms, total = 2
2024-12-12T17:49:43Z TRACE HTTP request body (http.request-body) listenerId = "https", localPort = 443, remoteIp = IPv6, remotePort = 39914,
contents = "{"type":"list","quota":0,"name":"foo","tenant":"TENANT","picture":"admin","secrets":["$6$SECRET"],"emails":["foo@example.org"],"urls":[],"memberOf":[],"roles":[],"lists":[],"members":[],"enabledPermissions":[],"disabledPermissions":[],"externalMembers":[]}", size = 353
2024-12-12T17:49:43Z DEBUG Management error (manage.error) listenerId = "https", localPort = 443, remoteIp = IPv6, remotePort = 39914, details = Invalid principal name, reason = Principal name must include a valid domain assigned to the tenant
2024-12-12T17:49:43Z TRACE HTTP response body (http.response-body) listenerId = "https", localPort = 443, remoteIp = IPv6, remotePort = 39914, contents = "{"error":"other","details":"Invalid principal name","reason":"Principal name must include a valid domain assigned to the tenant"}", code = 200, size = 129

Code of Conduct

• I agree to follow this project's Code of Conduct

[mdecimus]

When using tenants, the List Name has to be formatted as an email address and include one of the domains associated to the tenant. Intead of "Example" use "example@example.org" as the list name.

[ghz7l]

Ah, thanks, I get it.

Now, from an UI perspective, since the Tenant is the key factor, maybe it should be the first field. In which case the "Name" field should be something like a free text field with list-name as the placeholder, followed by @ followed by a drop-down menu for the available domains. In a single-tenant mode, any domain would do, and only the Tenant's domains would appear in the multi-tenant mode.

Then, the "Description" field should be renamed "Name", since the usual metaphor for email is "Name" <user@domain>, which makes both Name and Description confusing.

Also, since the "Name" @ "Domain" (currently Name) is an actual email address, it does not make sense to have another Email field: only aliases would make sense, if you want to have several mailing-list addresses (but I'm not sure what would the use-case be, besides aliasing some-list@lists.example.org to some-list@example.org).

BTW, super happy that mailing-lists can be used with external addresses. Any plan for web UI for listinfo and self-subscription?

[mdecimus]

Any plan for web UI for listinfo and self-subscription?

That is beyond the scope of the project at the moment, you need a mailing list software to handle automatic subscribe/unsubscribe.