Mbox

<h2 id="mail-storage-protocols">Mail storage protocols</h2>
<p>Unlike the Internet protocols used for the exchange of email, the format used for the storage of email has never been formally defined through the <a href="/facts/Request_for_Comments/esftTvE7">RFC</a> standardization mechanism and has been entirely left to the developer of an email client. However, the <a href="/facts/POSIX/mQkSt234">POSIX</a> standard defined a loose framework in conjunction with the <a href="/facts/Mailx/QMmV2M2J">mailx</a> program. In 2005, the application/mbox media type was standardized as RFC 4155, which hinted that mbox stores mailbox messages in their original Internet Message (RFC 2822) format, except for the used newline character, seven-bit clean data storage, and the requirement that each newly added message is terminated with a completely empty line within the mbox database.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>
</p>
<h2 id="file-locking">File locking</h2>

<p>Because more than one messages are stored in a single file, some form of <a href="/facts/File_locking/QektVCQs">file locking</a> is needed to avoid the corruption that can result from two or more processes modifying the mailbox simultaneously. This could happen if a network email delivery program delivers a new message at the same time as a mail reader is deleting an existing message.
</p><p>Various mutually incompatible mechanisms have been used by different mbox formats to enable message file locking, including fcntl() and lockf(). This does not work well with network mounted file systems, such as the <a href="/facts/Network_File_System_(protocol)/jWRRALVo">Network File System (NFS)</a>, which is why traditionally Unix used additional "dot lock" files, which could be created atomically even over NFS.
</p><p>Mbox files should also be locked while they are being read. Otherwise, the reader may see corrupted message contents if another process is modifying the mbox at the same time, even though no actual file corruption occurs.
</p>
<h2 id="as-a-patch-format">As a patch format</h2>
<p>In <a href="/facts/Open_source/7X9rCdz4">open source</a> development, it is common to send <a href="/facts/Patch_(Unix)/9tFn5GeU">patches</a> in the <a href="/facts/Diff/MtzRWwql">diff</a> format to a <a href="/facts/Mailing_list/jUsumebQ">mailing list</a> for discussion. The diff format allows for irrelevant "headers", such as mbox data, to be added.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> <a href="/facts/Version_control_system/pxCmFXqK">Version control systems</a> like <a href="/facts/Git/U5Ty9QmQ">git</a> have support for generating mbox-formatted patches and for sending them to the list as emails in a thread.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a><a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Maildir/styR8olS">Maildir</a></li>
<li><a href="/facts/MIX_(email)/k747Ivos">MIX (email)</a></li>
<li><a href="/facts/MH_Message_Handling_System/f4CBduT8">MH Message Handling System</a></li></ul>

<h2 id="further-reading">Further reading</h2>
<ul><li><a href="http://qmail.org/qmail-manual-html/man5/mbox.html">qmail mbox manual page</a></li>
<li><a href="https://web.archive.org/web/20120529014601/http://www.imc.org/">Internet Mail Consortium</a> – Standards body</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Hall, E., ed. (September 2005). "Request for Comments: 4155 – The application/mbox Media Type". Internet Engineering Task Force. Archived from the original on 17 May 2021. Retrieved 17 May 2021. <a href="https://datatracker.ietf.org/doc/html/rfc4155" target="_blank">https://datatracker.ietf.org/doc/html/rfc4155</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Hall, E., ed. (September 2005). "Request for Comments: 4155 – The application/mbox Media Type". Internet Engineering Task Force. Archived from the original on 17 May 2021. Retrieved 17 May 2021. <a href="https://datatracker.ietf.org/doc/html/rfc4155" target="_blank">https://datatracker.ietf.org/doc/html/rfc4155</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Resnick, P., ed. (April 2001). "Request for Comments: 2822 – Internet Message Format". Internet Engineering Task Force. Archived from the original on 31 March 2023. Retrieved 17 May 2021. <a href="https://datatracker.ietf.org/doc/html/rfc2822" target="_blank">https://datatracker.ietf.org/doc/html/rfc2822</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>"Submitting patches: the essential guide to getting your code into the kernel — The Linux Kernel documentation". www.kernel.org. Archived from the original on 2019-10-27. Retrieved 2020-03-03. <a href="https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html" target="_blank">https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>Randal, Allison; Sugalski, Dan; Tötsch, Leopold (2003). "Patch submission". Perl 6 Essentials. O'Reilly Media, Inc. p. 14. ISBN 978-0-596-00499-6. <a href="978-0-596-00499-6" target="_blank">978-0-596-00499-6</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>"Git - git-format-patch Documentation". git-scm.com. Archived from the original on 2020-03-07. Retrieved 2020-03-03. <a href="https://git-scm.com/docs/git-format-patch" target="_blank">https://git-scm.com/docs/git-format-patch</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
<li id="fn:7"><p>"Git - git-send-email Documentation". git-scm.com. Archived from the original on 2020-02-21. Retrieved 2020-03-03. <a href="https://git-scm.com/docs/git-send-email" target="_blank">https://git-scm.com/docs/git-send-email</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li>
</ol>

Mbox open-in-new

Mbox