Best practice for username?

[johndo100]

Hi,
Thanks for your hard work.
I have several domains and I want to receive email and send from my self hosted sever as well.
At first I create some user with username without domain suffix but it seems to a bad idea.
For example I have 2 users:
user1 and user2 with their email user1@domainA, user2@domainB.
Every time I send email from those user the MAIL_FROM always be user1@domainA and user2@domainA.
How can I make it correct user1@domainA, user2@domainB.

Thank you very much.

[enaut]

That is probably the setting in your email client where you specify the from address... I guess you specified the wrong one there.

[johndo100]

Thank you!
I fixed it in my Thunderbird and it works.
I'm so confusing about directory. I'm not really get it.
Now I have only one directory "default" for 2 domains and it works but I read in the docs:
For SQL servers this is done by executing the domains [lookup query]
How can I choose which directory for each domain when I'm receiving the mail?
Thank you very much!

[Samonitari]

I have similar problems, as I am trying to migrate from a multi domain ldap-postfix-dovecot-rspamd-nextcloud-etc setup to ldap-stalwart-nextcloud-etc:

• I have separate baseDn-s for separate domains. Solution for stalwart is to search under the root DN, but is will produce other problems, see below. Postfix has the %d token for the email's domain part usable in lookups (as opposed to the single ? token in stalwart), which I can use as a part of basedn, like search_base = ou=people,dc=%d,dc=myldaproot in postfix configs (I organized the domains as nodes under LDAP's root, like dc=example1.com,dc=myldaproot...)
• I cannot use auth bind, as I must branch the LDAP tree based on the email's/login name's domain part, which is, as said, not available as a token
• the domain attribute filter is not clear for me: those should be existing objectClass=domain objects under the root dn, like domains = "(&(objectClass=domain)(dc=?))" if stalwart would validate the domains directly, but the line "Searches for objects that have an email address in a specific domain name" confuses me. I guess I could leave it as is, only if not for my next point.
• I have accounts under one domain that: has mailAlias with addresses containing their respective domain, but also a mail attribute pointing to another domain. So there is only one mailbox for accounts like these, but they have aliases (and nextcloud accounts, etc.) under another domains too. I don't yet understood fully its implications for stalwart, but I think it will be a problem, as there are multiple accounts with identical mail attribute (under different domain node, and only one node's dn matches the actual adress's domain). These forwarding account have a custom PostfixBookMailForward objeclass
• The latter cases have a sub variation: PostfixBookMailForward typed accounts could have outer mail attributes, so their accounts only functions as a relay to, like, gmail
• To elaborate, the postfix/dovecot uses full email addresses as login username, but nextcloud use just the uid (which is the localpart in mail) as username, and in it's webmail integration config, the @example1.com parts are appended to the mail login name.

Maybe it is a bit contrieved setup, but I have nextcloud instances, etc, and this was the simplest setup that I could came up, which also makes possible seamless LDAP login for postfix/dovecot, multiple nextcloud instances, and nextcloud's webmail. The nextclouds and their webmail ones only see (and have access to) their separate domain base dns, to give one reason to the branched ldap setup...