Download the PHP package hfig/mapi without Composer
On this page you can find all versions of the php package hfig/mapi. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package mapi
Short Description Pure PHP library for reading and manipulating Microsoft Outlook .msg messages (MAPI documents)
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package mapi
Hfig/MAPI
Introduction
Hfig/MAPI is a PHP library for reading and working with Microsoft Outlook/Exchange format email messages (.msg files, aka MAPI documents).
The library can parse MAPI documents, and programatically extract the properties and streams of the document.
It can be used to convert messages to RFC822 (MIME) format by utilising the Swiftmailer/Switfmailer library.
The library is ostensibly a port of the aquasync/ruby-msg library from the Ruby language. Some questionable PHP architectural decisions come from migrating Ruby constructs. Some awful, but functional, code comes from a direct migration of the Ruby library.
Compared to ruby-msg, this library:
- Does not implement a command line entry point for message conversion
- Only handles MAPI documents in
.msgfiles (or a PHP stream of.msgfile data) - Does not implement the conversion of RTF-format message bodies to plain text or HTML
- Has better support for decoding MAPI document properties
- Produces a more faithful MIME conversion of the MAPI document
Installation
Install using composer
Usage
Accessing document properties
Conversion to MIME
Property Names
MAPI property names are documented by Microsoft in an inscrutible manner at https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2007/cc815517(v%3doffice.12).
A list of property names available for use in this library is included in the MAPI/Schema/MapiFieldsMessage.yaml file.
Keeping with the convention of the ruby-msg library, message properties are converted to a nice name:
PR_DISPLAY_NAME=>display_namePR_ATTACH_FILENAME=>attach_filename- etc
About MAPI Documents
MAPI documents are Microsoft OLE Structured Storage databases, much like old .doc, .xls and .ppt files. They consist of an internal directory structure of streams of 4K blocks that resemble a virtual FAT filesystem. For economy reasons, every structured storage database contains a root stream which contains 64-byte blocks which in turn stores small pieces of data. For further information see Microsoft's documentation.
The PEAR library OLE can read these database files. However this PEAR library is ancient and does not meet any modern coding standards, hence it's kept entirely decoupled from the message parsing code of this library. Hopefully it can be replaced one day.
Alternatives
For PHP, installing the Kopano Core project on your server will make available ext-mapi, a PHP extension which implements allows access to a port of the low-level MAPI Win32 API.
See also:
Email::Outlook::Message(Perl)aquasync/ruby-msg(Ruby)JTNEF(Java)
All versions of mapi with dependencies
ext-bcmath Version *
ext-mbstring Version *
pear/ole Version ^1.0.0RC8
pear/pear-core-minimal Version ^1.10
symfony/yaml Version ^4.1||^5.0||^6.0
ramsey/uuid Version ^3.8||^4.0
psr/log Version ^1.0||^2.0||^3.0