wodMailbox 2.1.1

WeOnlyDo! Mailbox is a component that can be easily integrated into your applications to provide full management over mailboxes and message parsing.
Using wodMailbox, you can easily access mailbox, count messages, look at messages, count parts, save attachments, look at headers, delete messages etc.. When wodMailBox opens mailbox, it expects to find there either regular mailbox just as is used on UNIX systems (one file with full mail messages one after another) or just one message inside, just as Outlook Express saves .eml files.

When you need to parse received messages, it might be hard to check all the possibilities that one simple mail message may contain. We all used to receive simple email messages - few headers and body text. But, sometimes you get attachments, multipart messages, different encodings and stuff like that. It's almost the same for wodMailbox - it's light, quick and fully supports all mail related RFC's.

You can look on using wodMailbox for three main purposes:
When you want to access mail messages in the mailbox
When you want to access and parse one mail message
When you want to prepare and create new message

Using together with wodPop3Server and wodSmtpServer (or any other UNIX-alike server) you will notice that easiest way to store messages on per-user basis in files. So, one file contain all the messages for one user. If user moves to different computer or account, it's easiest this way to move his email also. Moreover, IMAP and similarly 'larger' protocols keep all the mailboxes this way - all users' messages in one file, on per-user basis.
Once you want to access such mailbox, you just pass it's reference to wodMailbox.Filename property, and call Lock method. At this moment, wodMailbox will open the mailbox and count all the messages for you, but trying to use as low amount of memory as possible. This way, it can open and parse large mailboxes (few megabytes is considered to be 'small' at this point) with ease.

What's new in this version: 2.1.1 August 12, 2007 * Encoder and Decoder objects not support in memory operations on BASE64 and Quoted-Printable text