[MU] Auto-complete does not suggest LDAP mailing lists addresses

[quantranhong1999]

Description of the bug

Given I am [email protected], auto-complete does not suggest LDAP mailing list [email protected] addresses and only suggests govmu.org addresses.

Reason: we are matching exactly the domain part https://github.com/linagora/tmail-backend/blob/master/tmail-backend/jmap/extensions-opensearch/src/main/java/com/linagora/tmail/james/jmap/OSEmailAddressContactSearchEngine.java#L182

Should we match the lists prefix too @chibenwa ?

(not reported so far by customers)

[chibenwa]

Should we match the lists prefix too @chibenwa ?

It's more complicated than that.

We should only advertise the list through auto-complete if the user has the right to write to the mailing list.
So it needs to be populated on a per-user basis...

We wouldlikely need a detailed LSC script that:

• adds open lists into domain ato-complete DB
• adds list which the guy is member of into the user DB (|(&(businessCategory=memberRestrictedList)(member=<userDN>))(businessCategory=ownerRestrictedList)(owner=<userDN>))
  (member lists with this user and a member + ownerlist with this user as a member)

And then its more about adding the 2 tasks into LSC...

@quantranhong1999 you want to create this task?

Reason: we are matching exactly the domain part https://github.com/linagora/tmail-backend/blob/master/tmail-backend/jmap/extensions-opensearch/src/main/java/com/linagora/tmail/james/jmap/OSEmailAddressContactSearchEngine.java#L182

I think there's a mis-understanding. Here domain just denote "looks up in the DB of the domain for that specific user"

It do not says "the contact should be scoped by domain" BTW we have no such limits as far as I am aware of.

[quantranhong1999]

Yes, indeed that would sound complicated.

adds list which the guy is member of into the user DB

We do not expose the user contact routes via webadmin (yet).

We wouldlikely need a detailed LSC script that

I am not sure the LSC is the right framework for the job. Maybe it "could" do the job but would be requiring tweaking around.

Initially, I thought quickly this could be a quick win. If this is complicated like this, maybe we should put this on hold until customers really ask for this side enhancement?

[chibenwa]

maybe we should put this on hold until customers really ask for this side enhancement?

+1 !