Preliminary Checks

• I checked that all ports are open and not blocked by my ISP / hosting provider.

• I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

• I searched the issue tracker but was unable to find my issue.

• I read

  • the extended documentation in general but found nothing to resolve the issue;
  • the documentation on debugging, tried the proposed steps to debug the problem, but was still unable to resolve the issue;
  • this project's Code of Conduct and I agree;
  • the documentation about filing a bug report.

What operating system is the host running?

Linux

Which operating system version?

Debian 11

What computer architecture is the host running?

AMD64 (x86_64)

What container orchestration tool are you using?

Docker Compose

DMS version

v12.1.0

What happened and when does this occur?

This issue is similar to #3350 and #3262.

I want to create group aliases, as described in #3262 (comment) : a fairly simple setup involving two existing mailboxes and an alias used to redirect a mail to those two mailboxes.

Those mailboxes are not external: they are hosted by our DMS instance, unlike the aforementioned bug reports, hence this new report.

In the following example, both domain.org and other-domain.org are hosted on our DMS instance.

$> ./setup.sh email add [email protected]
Enter Password:
$> ./setup.sh email add [email protected]
Enter Password:
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias list | grep group
* [email protected] [email protected],[email protected]
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
[  ERROR  ]  '[email protected]' is already an alias for recipient: '[email protected]'
[  ERROR  ]  Aborting
$> ./setup.sh alias del [email protected] [email protected]
$> ./setup.sh alias del [email protected] [email protected]
$> ./setup.sh alias del [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
$> ./setup.sh alias add [email protected] [email protected]
[  ERROR  ]  '[email protected]' is already an alias for recipient: '[email protected]'
[  ERROR  ]  Aborting

It seems that DMS lets me create one group alias, but creating the second always fails somehow.
It may be linked to our usage of DMS with multiple domain names.

Am I doing something wrong, or is it an unintended side effect of #3270 ?

What did you expect to happen?

I expect to see created aliases without issue.

I agree on the idea of preventing aliases from being accounts (which is the initial goal of #3270), though it seems to have introduced bugs in the alias add feature.

Container configuration files

[Docker-compose file](https://git.42l.fr/42l/core/src/branch/root/services/mail/docker-compose.yml)

Relevant log output

No response

What level of experience do you have with containers, mail servers, and using a terminal?

• I am inexperienced with containers
• I am rather experienced with containers
• I am inexperienced with mail servers
• I am rather experienced with mail servers
• I am uncomfortable with using a terminal (CLI)
• I am rather comfortable with using a terminal (CLI)

Improvements to this form?

No response