Like MH, it stores each Email in a file of its own, but does not require any locking, ever. This avoids many problems with concurrent updates, such as that some programs use flock(2) while others use fcntl(2), or that NFS FileSystems may not even support locking, or make too few guarantees about it. To that end, MailDir imposes more complex naming and structural requirements than MH.
Rather than storing the files in a single directory, a MailDir MailBox uses three subdirectories: tmp, new and cur. tmp is a spool directory for new mail, used to ensure reliable delivery. Delivered, unread mail goes into the new subdirectory. As messages are read, they are moved into cur.
MailDir message naming conventions are defined so that message names are unique across shared filesystems, which means you don't get the normal set of file locking issues using most other formats. Some message flags and, depending on software, other MetaData, is encoded into the filename as well, to avoid the need to open every file all the time.
MailDir variants are used by Cyrus and courier IMAP daemons. Other MTAs have MailDir support, such as Exim and Postfix. The procmail(1) MDA also supports it, as do many MailClients such as Mutt and Evolution.
lib/main.php:944: Notice: PageInfo: Cannot find action page
lib/main.php:839: Notice: PageInfo: Unknown action
lib/plugin/WlugLicense.php:99: Warning: Invalid argument supplied for foreach()