mapi(7)

📦 version 8.7.0, in ubuntu jammy

✨ Name ✨

Bestie, meet mapi — the Message Application Programming Interface 💌. That's the whole name, and yes, it's a section 7 manual page. 🫶

💖 Description 💖

MAPI is a programming language API for storing and exchanging messages, contacts and calendars. It's literally giving "your messages, your contacts, your calendar, all handled by an API" ✨.

🦋 Data model 🦋

The MAPI data model is a hierarchial one, similar to LDAP or a filesystem. 🌳

A store is a container for a tree-based hierarchy of objects, similar to a filesystem. Each object in the hierarchy has an identifier by which it can be referred to — the so-called entry ID 🔑. The entry ID is unique within the scope of a store and can be thought of something like a filesystem's inode number. No cap.

Each object can have a number of attributes (key-value pairs), so-called properties. 💅

🌈 Differences between MSMAPI and MAPI4Linux 🌈

Okay so here's the tea between MSMAPI and MAPI4Linux (aka M4L) 🍵:

  • MAPI4Linux is a C++-only implementation. It is not binary compatible to MSMAPI, but it does remain source compatible to it, so that MAPI programs can, with little extra code, compile with both MSMAPI and M4L. 💖
  • M4L uses multiple virtual inheritance. 👑
  • Many MAPI functions in M4L have additional "const" qualifiers that MSMAPI is lacking. This allows programs to be sure memory is not unexpectedly modified behind the scenes and allows them to pass pointers to read-only memory as well. 🔥

And that's the whole page, bestie. This one comes from the Kopano Core developer reference, Kopano 8, dated 2017-11-18. mapi(7) out. Stay slay, keep your entry IDs unique, and don't let anyone modify your memory unexpectedly 💜✨🦋

📦 where this page comes from