LDAP support

[blaggacao]

If hackers want to interact with something like a corporate or organizational structure, they won't be able to avoid LDAP. Here's an example of a mutt query script which provides that feature in the broader ecosystem: https://github.com/qsuscs/mutt-addressbook

Use casese edging a professional use of Himalaya may be a big argument for adoption (as it may help increase the standards and iteroperability across the ecosystem). It would hackers to easily maintain their dream mail system in an organizational context. And it would allow future downstream MUAs (Thunderbird, anyone ?!?) to leverage strong foundations.

[soywod]

I don't know enough about the protocol. Is it possible to modify contacts via LDAP? If so then it can even become a new backend, next to vdir and CardDAV.

[blaggacao]

LDAP is essentially an SQL-ish for "directory services" over the air.

• You can define schemata (e.g. contact schema / person schema / identity schema / physical asset schema) - here: standardized contact & calendar schema
• You can have read or write permissions (hence update the data)

Insofar, indeed, it can become a new backend next to vdir & CardDAV. That seems the most sensible approach.

A widely referenced schema for contacts is inetOrgPerson:

• https://backstage.forgerock.com/docs/ds/7/schemaref/oc-inetOrgPerson.html / https://datatracker.ietf.org/doc/html/rfc2798

For calendar, there seems to be:

• https://backstage.forgerock.com/docs/ds/7/schemaref/oc-calEntry.html / https://datatracker.ietf.org/doc/html/rfc2739

[soywod]

I would be curious to see if LDAP can indeed be a new backend next to Vdir and CardDAV. I mean, if it has all the features like listing containers (addressbooks) and cards (contacts).