BUG? User-shared mailboxes, shared through SOGo, not working for imap or Sogo

NethServer Version: latest + full updates
Module: Sogo

Nov 19 16:49:42 sogod [1129]: [ERROR] <0x0x55bd1b614320[NGImap4Connection]> could not select URL: imap://j.m.visser%40domain.com@localhost/Shared/: {RawResponse = “{ResponseResult = {description = “Mailbox doesn’t exist: Shared”; result = no; tagId = 6; }; }”; reason = “Mailbox doesn’t exist: Shared”; result = 0; }

Ok, I am about to kill myself, or SOGo, or Dovecot of all of 'em …

Why are my user-shared mailboxes not working.

In my dovecot.conf it has a shared name space with list=yes

Both imap and sogo display the shared name space.
Whatever I try, no user shows up under it in imap and for sogo, see above log entry.

Accounts come from a second nethserver running samba ad.
I have requested help before with sogo, but I doubt it is sogo related it imap has trouble with it as well.

I am by no means an expert at this and slowly losing it :frowning:

just tried it works out of the box with sogo

please can u check something

first verify that your shared mailbox exists

ll -la /var/lib/nethserver/vmail/vmail/Maildir/

verify that the name of your sharedmailbox is written in the postfix conf

less /etc/postfix/virtual

check that shared mailbox are enabled in the esmith database

config show dovecot

should be
SharedMailboxesStatus=enabled

alternatively you can create a new sharedemailbox in the netgui panel and check what is the output of /var/log/messages

tailf /var/log/messages

1 Like

something more, you must not clic on the ‘shared folder’ title but on the folder logo

I know I have to ‘unfold’ the Shared and Other users folders, and can do so in Sogo

[root@gr110 ~]# ll -la /var/lib/nethserver/vmail/vmail/Maildir/
total 24
drwx------ 6 vmail vmail 255 Nov 19 17:36 .
drwx------ 3 vmail vmail 21 Nov 10 10:22 …
drwx------ 2 vmail vmail 6 Nov 10 10:22 cur
-rw------- 1 vmail vmail 38 Nov 10 10:22 dovecot-acl
-rw------- 1 vmail vmail 36 Nov 19 16:05 dovecot-acl-list
-rw------- 1 vmail vmail 164 Nov 10 10:22 dovecot.index.log
-rw------- 1 vmail vmail 24 Nov 19 17:36 dovecot.mailbox.log
-rw------- 1 vmail vmail 8 Nov 19 17:36 dovecot-uidvalidity
-r–r–r-- 1 vmail vmail 0 Nov 19 16:06 dovecot-uidvalidity.5a119e0e
-rw------- 1 vmail vmail 0 Nov 10 10:22 maildirfolder
drwx------ 2 vmail vmail 6 Nov 10 10:22 new
-rw------- 1 vmail vmail 5 Nov 19 17:36 subscriptions
drwx------ 5 vmail vmail 154 Nov 19 22:14 .Support
drwx------ 2 vmail vmail 6 Nov 10 10:22 tmp

[root@gr110 ~]# ll -la /var/lib/nethserver/vmail/vmail@domain.com/Maildir/
total 0
drwx------ 2 vmail vmail 30 Nov 19 16:04 .
drwx------ 3 vmail vmail 21 Nov 19 16:04 …
-rw------- 1 vmail vmail 0 Nov 19 16:04 dovecot-acl-list
[root@gr110 ~]#

This has never been different, never ever have I seen mailboxes here.

[root@gr110 ~]# config show dovecot
dovecot=service
AdminIsMaster=disabled
DeletedToTrash=disabled
FtsLuceneStatus=enabled
ImapMaxLineLenght=2048
ImapStatus=enabled
KrbKeytabPath=/var/lib/dovecot/krb5.keytab
KrbPrimaryList=smtp,imap,pop
KrbStatus=enabled
LmtpInetListenerStatus=disabled
LogActions=disabled
MaxProcesses=400
MaxUserConnectionsPerIp=12
PopStatus=enabled
QuotaDefaultSize=20
QuotaStatus=disabled
SharedMailboxesStatus=enabled
SpamFolder=Junk
SpamRetentionTime=15d
TCPPorts=110,143,4190,993,995
TlsSecurity=required
access=green,red
status=enabled

[root@gr110 ~]# cat /etc/postfix/virtual
# ================= DO NOT MODIFY THIS FILE =================
# 
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at NethServer official site: https://www.nethserver.org
#
# 
#
# 10postmaster
#
## postmaster@ is defined below


#
# 20accounts -- ensure local delivery for our accounts
#



#
# 20pseudonyms
#

# fully qualified aliases (address@domain)
support@domain.com           vmail+Support

# generic aliases expansion (address@)
postmaster@domain.com        root

#
# 30unknown_recipients_mailbox -- catch-all mailboxes for unknown recipients
#
# -- Messages to unknown recipients are bounced --

/var/log/messages is kinda empty, /var/log/sogo/sogo.log contains this when sharing my t.account users inbox to j.m.visser:

Nov 19 22:24:57 sogod [1138]: 10.20.30.2 "GET /SOGo/so/t.account/Mail/0/folderINBOX/addUserInAcls?uid=j.m.visser HTTP/1.1" 204 0/0 0.272 - - 0 Nov 19 22:24:57 sogod [1138]: 10.20.30.2 "GET /SOGo/so/t.account/Mail/0/folderINBOX/userRights?uid=j.m.visser HTTP/1.1" 200 255/0 0.244 - - 0 Nov 19 22:25:01 sogod [1138]: 10.20.30.2 "POST /SOGo/so/t.account/Mail/0/folderINBOX/saveUserRights HTTP/1.1" 200 0/402 0.297 - - 4K

Group-shared mailboxes work fine, just the user-ones are giving me a headache, and I’m just not getting it :frowning:

Based on what you say, I should have mailboxes listed in vmail. I clearly do not … which then makes it logical why I do not see any user-shared mailboxes in the Other users section. Could this have to do with having an AD account provider on a different machine ?

Login as root (username*root) doesnt work either (just enabled it compared to previous posted dovecot config)

2017-11-19 23:03:21.143 sogod[1129:1129] ERROR(-[NGLdapSearchResultEnumerator nextObject]): does not support result references yet .. Nov 19 23:03:21 sogod [1129]: SOGoRootPage Login from '10.20.30.2' for user 't.account*root' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0 Nov 19 23:03:21 sogod [1129]: 10.20.30.2 "POST /SOGo/connect HTTP/1.1" 403 34/94 0.050 - - 0 Nov 19 23:03:34 sogod [1129]: <0x0x55bd1a653320[LDAPSource]> <NSException: 0x55bd1b7d7f80> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{"error_code" = 49; login = "samaccountname=t.account*root,dc=ad,dc=domain,dc=com"; }

…and this too is to be expected when sogo looks for users in AD I’d say. I just do not know what to do about it, or if anything even can be done to begin with.

Here is what I mean as viewed from SOGo:

I am sorry to have to ask, but are we talking about the same issue ? I just reinstalled a new Nethserver installation. Noticed I am required to use an account provider and at that point created a snapshot.

I then:

  1. installed Samba AD locally and created two users:
  • j.m.visser
  • t.account

Tested with two users, no succes. Removed Samba AD and made it OpenLDAP and repeated the exact same test. No success.

I logged in to SOGo webinterface with both and shared both inboxes to one another. They do not show up.
config getprop dovecot SharedMailboxesStatus returns enabled.

[root@gr110 Maildir]# config getprop dovecot SharedMailboxesStatus
enabled

My shared namespace looks like this:

Shared mailboxes are enabled
namespace SHARED_USERS {
  type = shared
  disabled = no
  separator = /
  prefix = Shared/%%n@domain.com/
  location = maildir:/var/lib/nethserver/vmail/%%u/Maildir:INDEXPVT=~/Maildir/shared/%%u
  subscriptions = no
  list = yes
}

The mentioned location is valid BUT misses the ‘shared’ folder:

[root@gr110 Maildir]# ls -al
total 28
drwx------. 6 vmail vmail 275 Nov 20 16:30 .
drwx------. 3 vmail vmail  21 Nov 20 16:00 ..
drwx------. 2 vmail vmail   6 Nov 20 16:00 cur
-rw-------. 1 vmail vmail  21 Nov 20 16:30 dovecot-acl
-rw-------. 1 vmail vmail  17 Nov 20 16:30 dovecot-acl-list
-rw-------. 1 vmail vmail 912 Nov 20 16:30 dovecot.index.log
-rw-------. 1 vmail vmail  24 Nov 20 16:16 dovecot.mailbox.log
-rw-------. 1 vmail vmail  51 Nov 20 16:02 dovecot-uidlist
-rw-------. 1 vmail vmail   8 Nov 20 16:16 dovecot-uidvalidity
-r--r--r--. 1 vmail vmail   0 Nov 20 16:00 dovecot-uidvalidity.5a12ee20
drwx------. 5 vmail vmail 108 Nov 20 16:16 .Junk
-rw-------. 1 vmail vmail   0 Nov 20 16:00 maildirfolder
drwx------. 2 vmail vmail   6 Nov 20 16:00 new
-rw-------. 1 vmail vmail   5 Nov 20 16:16 subscriptions
drwx------. 2 vmail vmail   6 Nov 20 16:00 tmp
[root@gr110 Maildir]# pwd
/var/lib/nethserver/vmail/t.account@domain.com/Maildir

The ‘shared’ folder would houde the INDEXPVT, but this folder doesnt exist. Sogo doesnt return any errors when I save the access-rights:

Nov 20 16:30:23 sogod [24326]: 192.168.50.38 "GET /SOGo/so/t.account/usersSearch?search=Jeroen HTTP/1.1" 200 117/0 0.018 - - 0 Nov 20 16:30:25 sogod [24326]: 192.168.50.38 "GET /SOGo/so/t.account/Mail/0/folderINBOX/addUserInAcls?uid=j.m.visser HTTP/1.1" 204 0/0 0.231 - - 0 Nov 20 16:30:25 sogod [24326]: 192.168.50.38 "GET /SOGo/so/t.account/Mail/0/folderINBOX/userRights?uid=j.m.visser HTTP/1.1" 200 255/0 0.196 - - 0 Nov 20 16:30:25 sogod [24318]: <0x0x563d3d85e3c0[SOGoActiveSyncDispatcher]> Sleeping 30 seconds while detecting changes in Ping... Nov 20 16:30:31 sogod [24326]: 192.168.50.38 "POST /SOGo/so/t.account/Mail/0/folderINBOX/saveUserRights HTTP/1.1" 200 0/405 0.243 - - 0

The Shared namespace is listed, but no mailboxes show up:

Using Thunderbird ACL plugin reveals this (notice the missing domain fot t.user):

What am I missing at this point … why Is my domain missing for t.user ?
In order to rule out any residual configurations, I reinstalled the server as well with both account providers, with no different outcome.

Edit: could that missmatch be my issue ?

Sorry to spam this topic, but I now kjnow for sure this is a bug or a configuration error in the default configuration.

If I use the Thunderbird ACL plugin to set permissions to t.account@domain.com and reload SOGo, the mailbox is displayed:

I will now go kill myself for wasting countless hours on debugging this in unrelated configurations :frowning:
If this is somehow my own error, please que me in to what it is I am doing wrong here :confused:

no I was talking about the shared folder feature of nethserver, not the internal one of sogo

I don’t know, I did not use this feature before, I cannot myself display the field ‘other users’

@giacomo it is possible that we protect the imap acl of a sogo change ?

by the way, you could also create a new imap account in the user setting to receive email of someone else. Ok it is just a workaround.

I don’t think so, AFAIK changes to ACLs are made using IMAP protocol. regardless of the client

1 Like

The issue is SOGo using only the username part of username@domain.com when setting ACL’s.

When ACL’s are set with for instance Thunderbird with ImapACL extension installed, to username@domain.com, everything starts working as expected.

This implies that it reads them different then it sets them. This seems a SOGo bug, possibly due to configuration, but maybe even dovecot as I remember having set them manually with doveadm iirc, to username@domain.com

@davidep some time ago you did a card (needs review) in the roadmap on the possibly removal of the @domain in vmail

does it is related ?

Haleluja. This is solved, for me at least, with major bug on the SOGo webmail and Exchange ActiveSync end:

username1: abc012@domain.com
username2: abct01@domain.com

email1: j.m.visser@domain.com
email2: t.account@domain.com

Special config:

config setprop sogod IMAPLoginFieldName mail
signal-event nethserver-sogo-update

Open ADUC:

  • set user e-mail to friendly email
  • rename user abc012 (to get rid of some references to abc012 and replace with j.m. visser, but leave login as is
  • do not rename abct01 for testing purpose

login with IMAP client (Thunderbird) and user-shared mailboxes are now displayed and working.
login with SOGo with abc012: shared mailbox is not displayed
login with SOGo with abct01: shared mailbox is displayed as abc012@domain.com

Keep in mind that in IMAP this is now fully working as expected and as I need, so I think the applied patch edits one field too much, where the config should actually use the pricipalname… this must be SOGo local.

In all, I dare say this is not a Nethserver issue, nor a dovecot issue, but a SOGo issue in both setting ACL permissions on mailboxes (leaving out the @domain.com part while trying to find the user with domainname attached) and processing the permissions.

If I leave out the mail address from the user AD properties, and default to abc0123@domain.com, sharing works as expected in SOGo too.

My knowledge is too limited to pinpoint the exact cause here … I’m glad I got this far :stuck_out_tongue:

@stephdl … which SOGo directive should I change back to userPrincipalName in order for SOGo to display the entered email address, but work with the username when going to the filesystem ?

SOGo: (The shared folder is a group mailbox)

Thunderbird:

It would be nice to be able to display the user display name below Shared in Thunderbird, but that is not as much as a bug as a feature request I would say :stuck_out_tongue:

The resulting new issue is both SOGo webclient and Exchange activesync implementation no longer find the mailbox. I can log in, I get an empty mailbox and no user-shared mailbox, but I do get the groiup-shared mailbox.

ls in …/nethserver/vmail reveals I know have a folder abc012@domain.com AND a j.m.visser@domain.com

I’d say that for my case the fix to get the alias to show, fixed too much, but this can be mended by using user-options. If we use the userPrincipalName, but set the desired email adres manually in SOGo settings and IMAP settings, all that remains are headers revealing a username, but the wanted alias is displayed to receiving users.

That is an idea to allow changing the host FQDN without moving Maildirs around. The internal identifier used by dovecot for ACLs could be affected too.

I want to read this thread carefully. Please give me some time to study it. Anyway I remember of troubles with SOGo and shared folders from the times of ns6.

1 Like

I created a lot of fuss in this topic, take my last input as leading please.

Setting ACL’s with SOGo, makes them inoperable for IMAP and SOGo.
Setting ACL’s with Thunderbird using IMAP ACL plugin, makes it work for both IMAP and SOGo.

Using the ‘fix’ to willfully use the AD mail property instead of userPrincipalName in SOGo configuration, makes IMAP work as desired, but breaks SOGo and Exchange Active Sync functionality, as it changes also the location where SOGo is looking for (and storing) mail.

I need to change the SOGo config and use userPrincipalName in one specific place to make SOGo read from there (and by extension EAX) and that part is fully functional.

The real issue is SOGo setting ACL’s wrong. That is, setting ACL’s through the webmail, will set the rights to user instead of user@domain.com. I dare say it is wrong, because it can not process them itself either. After setting ACL’s with Thunderbird and without using the ‘fix’ to use the AD mail property (and thus defaulting back to userPrincipalName) SOGo displays the user shared mailboxes as well.

So the real bug here is how SOGo sets the ACL’s.

1 Like

it could be a nice feature to be able to change the FQDN after the users are configured :slight_smile:

what did you modify please

That actually didn’t work either. This was an assumption that didn’t pan out.

I did discover that after setting the email and return address to the alias on the user imap settings page in sogo, most things start working as expected, inclusief geaderd. Annoyances left are purely visual on the user-end in the IMAP scenario. Will add screenshots when at work.

So … because I just wasnt sure where to look and what to set, and it seems not many people use this specific configuration, as well as confusion about what I was trying to do, I had a huge mess of assumptions running amok.

I have since cleaned that mess, and the end result is almost as I like it.

First of all, the SOGo bug regarding setting ACL’s is real in my perception, the rest is not.
The real issue is SOGo setting ACL's wrong. That is, setting ACL's through the webmail, will set the rights to user instead of user@domain.com. I dare say it is wrong, because it can not process them itself either. After setting ACL's with Thunderbird and without using the 'fix' to use the AD mail property (and thus defaulting back to userPrincipalName) SOGo displays the user shared mailboxes as well.

What follows is a quick and dirty on how to get my current config and what that does. It has several undocumented features that, once you know them, really help you out here, intended or not.

  1. install nethserver 1 with samba ad and create users user1 and user2
  2. install nethserver 2, join it to that AD, install SOGo
  3. create aliasses for both users; t.account@domain.com and t.account2@domain.com
  4. log-in to the SOGo web-interface and fill in the e-mail alias as shown below:
  5. open ADUC and set AD property mail to the e-mail alias

Note I did not apply the userPrincipalName fix for the IMAPLoginFieldName.

Logging into SOGo now displays:

IMAP thru Thunderbird shows:

Headers while sending mail from t.account@domain.com:

IMAP:

X-Spam-Status: No, score=0.0, required= 4.0
X-MS-Exchange-Organization-PCL: 0
X-MS-Exchange-Organization-SCL: 0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) * on
	server1.domain2.local * at Wed, 22 Nov 2017 09:39:28 +0100
X-Spam-Status: No, score=-0.0, hits=-0.0, required= 8, autolearn=no
	autolearn_force=no, shortcircuit=no
X-Spam-Report: * -0.5 ALL_TRUSTED Passed through trusted hosts only via SMTP
	* -0.0 BAYES_20 BODY: Bayes spam probability is 5 to 20%
	*      [score: 0.1791]
	*  0.5 JAM_SHORT_MAIL_WITH_URL Mail with less than 150 chars and containing
	*       an URL
X-Process: ESTProcessDone
Received: from server2.domain.com (172.16.1.12) by
 remote.domain2.nl (192.168.50.2) with Microsoft SMTP Server id
 8.3.485.1; Wed, 22 Nov 2017 10:22:38 +0100
Received: from server2.domain.com (localhost [127.0.0.1])	by
 server2.domain.com (Postfix) with ESMTP id C7F031802C393	for
 <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017 10:22:38 +0100 (CET)
Received: from [192.168.50.38] (unknown [192.168.50.38])	(Authenticated
 sender: lmst01)	by server2.domain.com (Postfix) with ESMTPSA	for
 <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017 10:22:38 +0100 (CET)
To: jeroenvisser@domain2.nl
From: Test Account <t.account@domain.com>
Subject: IMAP header test
Message-ID: <c6776887-38b1-0206-f95b-8ebf250d3bdb@domain.com>
Date: Wed, 22 Nov 2017 10:22:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: nl
X-Antivirus: Avast (VPS 171121-4, 21-11-2017), Outbound message
X-Antivirus-Status: Clean
Return-Path: t.account@domain.com
X-Antivirus: avast! (VPS 171121-4, 21-11-2017), Inbound message
X-Antivirus-Status: Clean

SOGo:

X-Spam-Status: No, score=-2.4, required= 4.0
X-MS-Exchange-Organization-PCL: 0
X-MS-Exchange-Organization-SCL: 0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) * on
	server2.domain2.local * at Wed, 22 Nov 2017 09:39:28 +0100
X-Spam-Status: No, score=-2.4, hits=-2.4, required= 8, autolearn=no
	autolearn_force=no, shortcircuit=no
X-Spam-Report: * -0.5 ALL_TRUSTED Passed through trusted hosts only via SMTP
	* -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
	*      [score: 0.0002]
	*  0.0 HTML_MESSAGE BODY: HTML included in message
X-Process: ESTProcessDone
Received: from server1.domain.com (172.16.1.12) by
 remote.domain2.nl (192.168.50.2) with Microsoft SMTP Server id
 8.3.485.1; Wed, 22 Nov 2017 10:25:51 +0100
Received: from server1.domain.com (localhost [127.0.0.1])	by
 server1.domain.com (Postfix) with ESMTP id 0F063180336F7	for
 <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017 10:25:51 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])	by server1.domain.com
 (Postfix) with ESMTP	for <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017
 10:25:50 +0100 (CET)
Content-Type: multipart/alternative;
	boundary="----=_=-_OpenGroupware_org_NGMime-5635-1511342750.890552-1------"
From: Test Account <t.account@domain.com>
Reply-To: t.account@domain.com
X-Forward: 192.168.50.38
Date: Wed, 22 Nov 2017 10:25:50 +0100
To: jeroenvisser@domain2.nl
MIME-Version: 1.0
Message-ID: <1603-5a154280-b-29a18ac0@211616679>
Subject: SOGo header test
User-Agent: SOGoMail 3.2.10
Return-Path: t.account@domain.com
X-Antivirus: avast! (VPS 171121-4, 21-11-2017), Inbound message
X-Antivirus-Status: Clean

EAX: (return path wrong)

X-Spam-Status: No, score=-0.6, required= 4.0
X-MS-Exchange-Organization-PCL: 0
X-MS-Exchange-Organization-SCL: 0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) * on
	server2.domain2.local * at Wed, 22 Nov 2017 10:39:42 +0100
X-Spam-Status: No, score=-0.6, hits=-0.6, required= 8, autolearn=ham
	autolearn_force=no, shortcircuit=no
X-Spam-Report: * -0.5 ALL_TRUSTED Passed through trusted hosts only via SMTP
	*  0.4 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
	*  0.0 HTML_MESSAGE BODY: HTML included in message
	* -0.5 BAYES_05 BODY: Bayes spam probability is 1 to 5%
	*      [score: 0.0256]
X-Process: ESTProcessDone
Received: from server1.domain.com (172.16.1.12) by
 remote.domain2.nl (192.168.50.2) with Microsoft SMTP Server id
 8.3.485.1; Wed, 22 Nov 2017 10:45:12 +0100
Received: from server1.domain.com (localhost [127.0.0.1])	by
 server1.domain.com (Postfix) with ESMTP id 03EB5180336F8	for
 <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017 10:45:12 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])	by server1.domain.com
 (Postfix) with ESMTP	for <jeroenvisser@domain2.nl>; Wed, 22 Nov 2017
 10:45:11 +0100 (CET)
From: Test Account <t.account@domain.com>
To: <jeroenvisser@domain2.nl>
Subject: EAX header test
Date: Wed, 22 Nov 2017 10:45:16 +0100
Message-ID: <001201d36376$9a34d200$ce9e7600$@domain.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0013_01D3637E.FBF98820"
X-Mailer: Microsoft Outlook 16.0
Content-Language: nl
Thread-Index: AdNjdpd2gB1RuivzQiaqcxBYqUJm8Q==
Return-Path: lmst01@domain.com
X-Antivirus: avast! (VPS 171121-4, 21-11-2017), Inbound message
X-Antivirus-Status: Clean

The only 3 issues left, are mainly aesthetic, but will cause users to moan. They are:

  1. SOGo Webinterface displaying the username instead of the email alias in top left
  2. IMAP (dovecot) will display the Shared mailbox using the username instead of the Full name or the email alias.
  3. Returnpath for EAX mail is using the username instead of the alias. Only shows in the header.

It seems I messed op some replace actions for domain and domain2, rendering the headers a bit confusing. The part that matters is that t.account is used and not lmst01 (the user in this scenario)

2 Likes