[root@NS7DEV3 ~]# rpm -qa nethserver-roundcubemail
nethserver-roundcubemail-1.2.4-1.3.g83cf3f6.ns7.noarch
[root@NS7DEV3 ~]# rpm -qa nethserver-mail-server
nethserver-mail-server-1.10.4-1.2.g5bff66e.ns7.noarch
the root user can login when you set the ‘local’ by the dropdown menu
the root@mydomain.com cannot login, but its is normal
I found two root folders after that
[root@NS7DEV3 ~]# ll /var/lib/nethserver/vmail/
total 4
drwx------ 3 vmail vmail 20 Nov 17 21:32 root
drwx------ 3 vmail vmail 20 Nov 17 21:30 root@stephdl.dyndns.org
-rw------- 1 vmail vmail 35 Nov 17 21:33 shared-mailboxes.db
drwx------ 4 vmail vmail 53 Nov 17 21:34 toto@stephdl.dyndns.org
drwx------ 3 vmail vmail 20 Nov 17 21:26 vmail
I don’t know if it is a side effect (we found also two root users in the mysql database of roundcubemail)
My concern is that it is not easy to know that you must choose ‘local’ to login with the root user. At least some doc should be done in the Admin manual.
When you use a user with the dropdown menu of your domain, whatever user@domain or user, are workable, only one user is created at
[root@NS7DEV3 ~]# ll /var/lib/nethserver/vmail/
total 4
drwx------ 3 vmail vmail 20 Nov 17 21:32 root
drwx------ 3 vmail vmail 20 Nov 17 21:30 root@stephdl.dyndns.org
-rw------- 1 vmail vmail 35 Nov 17 21:33 shared-mailboxes.db
drwx------ 4 vmail vmail 53 Nov 17 21:34 toto@stephdl.dyndns.org
drwx------ 3 vmail vmail 20 Nov 17 21:26 vmail
we can see that in mysql
MariaDB [roundcubemail]> SELECT * FROM users
-> ;
+---------+-------------------------+-----------+---------------------+---------------------+----------+-------------------------------------------------------------------+
| user_id | username | mail_host | created | last_login | language | preferences |
+---------+-------------------------+-----------+---------------------+---------------------+----------+-------------------------------------------------------------------+
| 1 | root | localhost | 2016-11-17 21:30:08 | 2016-11-17 21:30:08 | fr_FR | a:1:{s:11:"client_hash";s:32:"c3a2e50f09a41581d9db4ada516a09c6";} |
| 2 | root | 127.0.0.1 | 2016-11-17 21:32:28 | 2016-11-17 21:32:28 | fr_FR | a:1:{s:11:"client_hash";s:32:"dff655bc1073ab1d5ae392c238fcd307";} |
| 3 | toto@stephdl.dyndns.org | localhost | 2016-11-17 21:33:36 | 2016-11-17 21:39:07 | fr_FR | a:1:{s:11:"client_hash";s:32:"c9f1cf9fba3ddf72be7368177390a3f1";} |
+---------+-------------------------+-----------+---------------------+---------------------+----------+-------------------------------------------------------------------+
3 rows in set (0.00 sec)
I created a sieve rule to drop to the junk folder all email with a specific object, it is workable whater the user or user@domain form of login
4 /var/lib/nethserver/vmail/toto@stephdl.dyndns.org/Maildir/.Junk/cur/1479415098.M906084P16357.NS7DEV3.stephdl.dyndns.org,S=939,W=959:2,
4 /var/lib/nethserver/vmail/toto@stephdl.dyndns.org/Maildir/.Junk/cur/1479415174.M914169P16438.NS7DEV3.stephdl.dyndns.org,S=1000,W=1024:2,
Here the sieve script used
[root@NS7DEV3 ~]# cat /var/lib/nethserver/vmail/toto@stephdl.dyndns.org/.dovecot.sieve
require ["fileinto"];
# rule:[plop]
if header :contains "subject" "plop"
{
fileinto "Junk";
}