This is possible, without problems. At least using NethServer, NextCloud and Roundcube.
I can’t confirm SoGo or WebTop as I don’t use both.
In Roundcube you need to set the user ID and who the user is sending as.
In a multidomain setup, the most common use case is for the webmaster@domainname.com mail, but also for the info@domainname.com mail account. Other accounts can have conflicts, but the two mentionned will ALWAYS have conflicts on a multidomain setup, so these need to be done right.
• domain1.tld. 86400 IN A 123.456.111
• *.domain1.tld. 86400 IN A 123.456.111
• www.domain1.tld. 86400 IN A 123.456.111
• imap.domain1.tld. 86400 IN A 123.456.111
• smtp.domain1.tld. 86400 IN A 123.456.111
• wp.domain1-tld. 86400 IN A 123.456.111
• srv01-domain1.tld. 86400 IN A 123.456.111
• domain1.tld. 86400 IN MX 10 domain1.tld.
• _dmarc. domain1.tld.86400 IN TXT "v=DMARC1; p=quarantine"
• default._domainkey. domain1.tld. 86400 IN TXT ( "v=DKIM1; k=rsa; " "p=ML2BIg…" " +jIB…" )
domain2.tld (existing Plesk installation, should be migrated to nethserver)
• domain2.tld. 86400 IN A 123.456.222
…
• domain2.tld. 86400 IN MX 10 domain2.tld.
• *._tcp. domain2.tld. 86400 IN TLSA 3 1 1 987abc321…
• _imaps._tcp. domain2.tld. 86400 IN SRV 0 0 993 domain2.tld.
• _pop3s._tcp. domain2.tld. 86400 IN SRV 0 0 995 domain2.tld.
• _smtps._tcp. domain2.tld. 86400 IN SRV 0 0 465 domain2.tld.
Mail Domains (Nethserver —> Email —> Domains):
• domain1.tld as Standard-Domain (DKIM configured)
Status Check: Port 25 o.k. || DKIM-Record o.k. || MX-Record o.k. || IP reverse o.k.)
• domain2.tld as Alias-Domain (DKIM not configured)
Status Check: Port 25 unreachable || DKIM-Record missing record || MX-Record o.k. || IP reverse o.k.)
→ The differences between an alias domain and a standard domain and their effects on server configuration and client configuration are not explained in the manual.
C) User Management
System User (LDAP):
• admin (groups: domain admins)
• user1 (groups: domain mail)
• user2 (groups: domain admins; mail)
missing Mail stores (/var/lib/nethserver/vmail):
• /user2@domain2.tld/ (because redirected to user2, that means to user2@domain1.tld)
D) What I Need:
• Some users with existing mail addresses and unique mailboxs on domain2.tld
• user2@domain2.tld,…user6@domain2.tld, , …
E) What should I do?
a) If I create the system the user (LDAP) like user5, user6, …they automatically get the mail address user5@domain1.tld, user6@domain1.tld…
b) If I create an additional mail address “user5@domain2.tld”, “user6@domain2.tld”, … I have to specify a destination, redirecting to an existing system user…and this system user is related to a mail address and mail store with “domain1.tld”
c) I am completely at a loss as to what to do now.
Does anything change in the described behavior if I change the A-record from domain2.tld to the new Nethserver and then create the vhost, system and mail-user or is it indifferent? Which MX-record do I have to create then? MX 10 domain1.tld or MX 10 domain2.tld?
d) How do i have to configure my mail client to create a mailbox for user5@domain2.tld and send and receive mails exclusively for user5@domain2.tld?
Could you explain how do you resolved this kind of problem, or better how I shell resolve my problems?
Possibly I still have a thinking error. @mrmarkuz disillusioned me now I have hope again.
The first part is the actual username, this can recieve mail, but as no one knows about it, it’s never used. This is basically just a username, for clients to log in…
The second part is the email alias (What is actually used for reception of mails.
Outgoing is set in the client. (Thunderbird, Mac Mail, Outlook, etc.)
If using Webmail like Roundcube, just set that for each user in roundcube. (Settings / Identity)
This should solve your mail / user account problems, or at least suggest a naming convention which works!
My 2 cents
Andy
PS: personally, i put the domain-identifier at the end: username_dom1…
What is your advice? Should I change the DNS-record before or after the Nethserver configuration?
I would prefer a change after the Nethserver configuration, because my existing server can work without interruption.
A DNS always takes time before it is “available” on the internet. A key in this is TTL (Time To Live, or how long can the record last for…). Usually you set TTL lower a week or more before the move…
After a successful move, TTL is set higher again.
As long as your nethserver can resolve itself in the meantime, do Nethserver first, and DNS later.
@Andy_Wismer … You’re the best!
Mail switch is done, all works fine.
Right now I’m struggling with the final Wordpress migration. Something is not working as expected.
We need to add a piece of code to the wp-config.php configuration file, so that WordPress has no problem performing certain functions, such as updating, or it will be unable to locate the content directory and will display an error message.
and the best…I got a working system and had a wonderful learning curve.
This is mainly due to the perseverance and the ability to suffer of those involved.
I can vividly imagine how they turned their eyes from time to time.