Mbox - Revision history

Dexvertbot: /* Sample files */

2023-12-28T03:22:17Z

‎Sample files

Dexvertbot: Undo revision 46514 by Dexvertbot (talk)

2023-12-28T03:03:15Z

Undo revision 46514 by Dexvertbot (talk)

Dexvertbot: Change telparia.com samples link to template

2023-12-28T02:53:14Z

Change telparia.com samples link to template

Sembiance: /* Sample files */

2021-07-30T17:14:17Z

‎Sample files

Sembiance: Added sample file

2020-05-26T14:07:24Z

Added sample file

Jsummers: PRONOM

2015-02-21T02:57:03Z

PRONOM

Dan Tobias at 01:41, 28 January 2015

2015-01-28T01:41:48Z

Dan Tobias at 01:41, 28 January 2015

2015-01-28T01:41:31Z

Dan Tobias at 12:49, 21 September 2014

2014-09-21T12:49:56Z

Dan Tobias at 02:30, 20 September 2014

2014-09-20T02:30:22Z

@@ Line 31: / Line 31: @@
 == Sample files ==
-* https://telparia.com/fileFormatSamples/archive/mbox
+* {{DexvertSamples|archive/mbox}}
 == Links ==

@@ Line 31: / Line 31: @@
 == Sample files ==
-* {{DexvertSamples|archive/mbox}}www.qmail.org/man/man5/mbox.html Qmail man page]
+* https://telparia.com/fileFormatSamples/archive/mbox
 * [http://docs.python.org/2/library/mailbox.html Python library to handle mailbox formats]
 * [http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html More discussion of mbox format versions]
 * [http://kb.mozillazine.org/Recover_messages_from_a_corrupt_folder Info on fixing corrupt mbox files of the form used by Mozilla Thunderbird]

@@ Line 31: / Line 31: @@
 == Sample files ==
-* https://telparia.com/fileFormatSamples/archive/mbox
+* {{DexvertSamples|archive/mbox}}www.qmail.org/man/man5/mbox.html Qmail man page]
-−
-== Links ==
-−
-* RFC 4155 (application for MIME type, defines format)
-* [[Wikipedia:mbox|Wikipedia article]]
-* [http://www.qmail.org/man/man5/mbox.html Qmail man page]
 * [http://docs.python.org/2/library/mailbox.html Python library to handle mailbox formats]
 * [http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html More discussion of mbox format versions]
 * [http://kb.mozillazine.org/Recover_messages_from_a_corrupt_folder Info on fixing corrupt mbox files of the form used by Mozilla Thunderbird]

@@ Line 31: / Line 31: @@
 == Sample files ==
-* https://telparia.com/fileFormatSamples/archive/alt.crafts.scrapbooks.20140428.mbox
+* https://telparia.com/fileFormatSamples/archive/mbox
 == Links ==

← Older revision		Revision as of 14:07, 26 May 2020
Line 29:		Line 29:

	* '''mboxcl2''': A variant of ''mboxcl'' which uses "Content-Length" headers to find messages, and doesn't do any "From " escaping. This avoids corrupting message bodies, but could get into trouble if a message has a missing or incorrect content length header, or if the file is processed by a mailer or utility that expects to be able to split messages by "From " headers. (LOCFDD {{LoCFDD\|fdd000387}})		* '''mboxcl2''': A variant of ''mboxcl'' which uses "Content-Length" headers to find messages, and doesn't do any "From " escaping. This avoids corrupting message bodies, but could get into trouble if a message has a missing or incorrect content length header, or if the file is processed by a mailer or utility that expects to be able to split messages by "From " headers. (LOCFDD {{LoCFDD\|fdd000387}})
		+
		+	== Sample files ==
		+	* https://telparia.com/fileFormatSamples/archive/alt.crafts.scrapbooks.20140428.mbox

	== Links ==		== Links ==

@@ Line 4: / Line 4: @@
 |mimetypes={{mimetype|application/mbox}}
 |locfdd={{LoCFDD|fdd000383}}, {{LoCFDD|fdd000384}}, {{LoCFDD|fdd000385}}, {{LoCFDD|fdd000386}}, {{LoCFDD|fdd000387}}
 |extensions={{ext|mbx}}
 |released=1970s
 }}
 '''mbox''' is the format typically used in Unix-like systems for storing collections of e-mail messages, dating back to the early days of Unix and UUCP network connections. It has several minor variants, but they all consist of a series of messages in [[Internet e-mail message format]] (RFC 822 and its successors) appended together, including headers and body. The entire file is supposed to be in 7-bit [[ASCII]], with any characters outside that range encoded in some manner (in accordance with various other standards for character encoding in messages and their component parts and attachments). Traditional old-school Unix systems didn't generally use file extensions, so many mbox files are extensionless, but some other systems (e.g., [[Eudora]]) use a .mbx extension.

@@ Line 8: / Line 8: @@
 }}
-'''mbox''' is the format typically used in Unix-like systems for storing collections of e-mail messages, dating back to the early days of Unix and UUCP network connections. It has several minor variants, but they all consist of a series of messages in [[Internet e-mail message format]] (RFC 822 and its successors) appended together, including headers and body. The entire file is supposed to be in 7-bit [[ASCII]], with any characters outside that range encoded in some manner (in accordance with various other standards for character encoding in messages and their component parts and attachments). Traditional old-school Unix systems didn't generally use file extensions, so many mbox files are extensionless, but some other systems (e.g., Eudora) use a .mbx extension.
+'''mbox''' is the format typically used in Unix-like systems for storing collections of e-mail messages, dating back to the early days of Unix and UUCP network connections. It has several minor variants, but they all consist of a series of messages in [[Internet e-mail message format]] (RFC 822 and its successors) appended together, including headers and body. The entire file is supposed to be in 7-bit [[ASCII]], with any characters outside that range encoded in some manner (in accordance with various other standards for character encoding in messages and their component parts and attachments). Traditional old-school Unix systems didn't generally use file extensions, so many mbox files are extensionless, but some other systems (e.g., [[Eudora]]) use a .mbx extension.
 Some problems and incompatibilities of this format stem from the (rather shortsighted, in hindsight) design decision to have as the separator indicating the boundary between messages a "From" line inserted by the mailer program; messages are split based on the characters "From " (with a trailing space) appearing at the beginning of a line. This is distinct from the "From:" line in the headers of a message, which has a colon after it. The From line that is used as a separator follows that keyword with the originating mailbox name (originally a [[UUCP]] "[[bang path]]", with a series of nodes separated by exclamation points showing how the message got from its originating node to the place it currently was) then the date and possibly other information.

@@ Line 9: / Line 9: @@
 '''mbox''' is the format typically used in Unix-like systems for storing collections of e-mail messages, dating back to the early days of Unix and UUCP network connections. It has several minor variants, but they all consist of a series of messages in [[Internet e-mail message format]] (RFC 822 and its successors) appended together, including headers and body. The entire file is supposed to be in 7-bit [[ASCII]], with any characters outside that range encoded in some manner (in accordance with various other standards for character encoding in messages and their component parts and attachments).
-Some problems and incompatibilities of this format stem from the (rather shortsighted, in hindsight) design decision to have as the separator indicating the boundary between messages a "From" line inserted by the mailer program; messages are split based on the characters "From " (with a trailing space) appearing at the beginning of a line. This is distinct from the "From:" line in the headers of a message, which has a colon after it. The From line that is used as a separator follows that keyword with the originating mailbox name (originally a UUCP "bang path", with a series of nodes separated by exclamation points showing how the message got from its originating node to the place it currently was) then the date and possibly other information.
+Some problems and incompatibilities of this format stem from the (rather shortsighted, in hindsight) design decision to have as the separator indicating the boundary between messages a "From" line inserted by the mailer program; messages are split based on the characters "From " (with a trailing space) appearing at the beginning of a line. This is distinct from the "From:" line in the headers of a message, which has a colon after it. The From line that is used as a separator follows that keyword with the originating mailbox name (originally a [[UUCP]] "[[bang path]]", with a series of nodes separated by exclamation points showing how the message got from its originating node to the place it currently was) then the date and possibly other information.
 Because "From" is a common English word which often appears in the body of messages, sometimes at the beginning of lines, "escaping" has to be done by the mailer programs to alter such lines so they are not mistaken for message breakpoints. This is usually done by prefixing the line with a greater-than sign (>).

@@ Line 21: / Line 21: @@
 The known variants (in terminology dating to the 1990s):
-* '''mboxo''': The "original" mbox format, which escapes "From " lines in a non-reversible manner.
+* '''mboxo''': The "original" mbox format, which escapes "From " lines in a non-reversible manner. (LOCFDD {{LoCFDD|fdd000384}})
-* '''mboxrd''': Version using "reversible" escaping where the ">" signs are piled on and are supposed to be stripped later; named after its inventor, Rahul Dhesi. [[Thunderbird]] uses this type of file.
+* '''mboxrd''': Version using "reversible" escaping where the ">" signs are piled on and are supposed to be stripped later; named after its inventor, Rahul Dhesi. [[Thunderbird]] uses this type of file. (LOCFDD {{LoCFDD|fdd000385}})
-* '''mboxcl''': From Unix System V; uses "Content-Length" headers in the individual messages to determine where to find the next message, so it doesn't need to scan for "From " lines. However, this format ''still'' escapes "From " lines in message bodies (in the non-reversible manner of ''mboxo'') anyway, making the whole thing seem pretty pointless.
+* '''mboxcl''': From Unix System V; uses "Content-Length" headers in the individual messages to determine where to find the next message, so it doesn't need to scan for "From " lines. However, this format ''still'' escapes "From " lines in message bodies (in the non-reversible manner of ''mboxo'') anyway, making the whole thing seem pretty pointless. (LOCFDD {{LoCFDD|fdd000386}})
-* '''mboxcl2''': A variant of ''mboxcl'' which uses "Content-Length" headers to find messages, and doesn't do any "From " escaping. This avoids corrupting message bodies, but could get into trouble if a message has a missing or incorrect content length header, or if the file is processed by a mailer or utility that expects to be able to split messages by "From " headers.
+* '''mboxcl2''': A variant of ''mboxcl'' which uses "Content-Length" headers to find messages, and doesn't do any "From " escaping. This avoids corrupting message bodies, but could get into trouble if a message has a missing or incorrect content length header, or if the file is processed by a mailer or utility that expects to be able to split messages by "From " headers. (LOCFDD {{LoCFDD|fdd000387}})
 == Links ==