[bug]: Primary and Alias addresses are switched when using MySQL as storage and authentication

[Har-Kuun]

What happened?

In the case MySQL as storage backend and the authentication directory, when a user is assigned a primary address and an alias address through the database, the Stalwart seems to display the alias as the primary address and the primary address as the alias.

This seems more like a display/cosmetic problem, not affecting real login/usage though.

How can we reproduce the problem?

1. Set up MySQL as the storage and authentication backend for Stalwart.
2. Create a user with a primary address and an alias address
3. Stalwart displays the swapped addresses.

DB Schema:

Relevant data entries:

Stalwart admin portal:

Version

v0.11.x

What database are you using?

mySQL

What blob storage are you using?

mySQL

Where is your directory located?

SQL

What operating system are you using?

Linux

Relevant log output

Code of Conduct

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

[mdecimus]

Please provide the SQL queries you are currently using to obtain account details and email addresses.

[Har-Kuun]

Query account details:
SELECT name, type, secret, description, quota FROM accounts WHERE name = ? AND active = true

Query emails:
SELECT address FROM emails WHERE name = ? ORDER BY address ASC

Thank you

[andreymal]

Well, ORDER BY address ASC obviously moves @example.com before [email protected]

The documentation suggests ORDER BY type DESC, address ASC

^{(but personally I'd replace the type column with a numeric column for ordering)}

[Har-Kuun]

Ah... I see, didn't realize this is done by SQL sorting. I though there was a separate internal query using something like WHERE type = 'primary' for this purpose. Thanks! Fixed now.