exchange_nsp(4gx)

💖 exchange_nsp(4gx) 💖

Gromox admin reference energy, bestie — and the manual name is literally exchange_nsp(4gx). This page is the handler for the Name Service Provider Interface Protocol. Slay.

✨ NAME ✨

exchange_nsp — Handler for the Name Service Provider Interface Protocol

🌸 DESCRIPTION 🌸

okay so exchange_nsp is a component for http(8gx) that handles the Name Service Provider Interface Protocol. In essence, it's providing the Address Book for Outlook's EMSMDB32.DLL connector. That's the whole vibe: NSPI protocol in, address book out, no cap. 🫶

🎀 CONFIGURATION DIRECTIVES 🎀

The usual config file location is /etc/gromox/exchange_nsp.cfg. Keep that path close, iykyk.

• cache_interval — Default: 5 minutes
• hash_table_size — Default: 3000
• nsp_trace — Level 1: Log entry into and exit out of NSP functions, with their parameter values to stderr (not http_log_file!). Log data dumps of select calls. Level 2: Dump more data. Default: 0
• x500_org_name — Default: (unspecified)

🦋 NOTES 🦋

A number of properties are always synthesized by exchange_nsp and never read from any storage; this includes key properties such as PR_ENTRYID, PR_RECORD_KEY, etc. Not me pointing out that these are homegrown, bestie — they're just built in.

For user-attached properties that are read from SQL (cf. table "user_properties"), exchange_nsp (as well as zcore(8gx)'s AB) only handles a subset of property types: PT_BOOLEAN, PT_SHORT, PT_LONG, PT_I8, PT_SYSTIME, PT_BINARY, PT_UNICODE/STRING8 and PT_MV_UNICODE/STRING8. That's the list — periodt. 💅

🌈 SIGNALS 🌈

Upon receipt of SIGHUP, the address book cache will be dropped; the next regular request for the AB will cause it to be reloaded.

• MS-OXNSPI: Exchange Server Name Service Provider Interface (NSPI) Protocol

🔥 SEE ALSO 🔥

gromox(7), http(8gx)

---

footer source/version sign-off: Gromox, page exchange_nsp(4gx). The date isn't showing up on this page, so I'm not gonna invent one, bestie — just sending you off with a cute wave 🫶💅✨