The Internet Messaging Application Protocol (IMAP) is highly appreciated because of many reasons, such as the cross compatibility with multiple email clients, but at the same time, it has its drawbacks. The most infamous disadvantages of the IMAP protocol are those related to the faulty disk space management. These disk space management problems can affect both the server side and the user quota, and they are one of the main reasons why the IMAPSize application has been created.
IMAPSize is a feature-rich IMAP mail account manager created to be more than just an average mail client. It was created to enable the users to easily find out which mail directories take the most space. Therefore, they will be able to keep their storage quota under control in a much easier manner.
Its interface is simple and neat, but in order to be able to use this tool you have to know how to specify the account data related to your IMAP mail account, including username, password, server and port data. Then the content of your mailbox will be displayed, with focus on the sizes of each mail directory. The messages from each mail folder can also be easily retrieved and viewed. Besides the neat interface, I also like the fact that this tool comes with a lot of handy additional features and settings. The highly-configurable search capabilities, the e-mail attachment management options, the support for SSL connections, the backup related features (support for incremental backups is also provided) and the support for performing conversions between EML and MBOX files are just a few examples of the many things that this application offers.
In conclusion, IMAPSize is a great solution for anyone in need of keeping their IMAP accounts under strict control. The fact that it is free makes me like it even more.
v0.3.7 [Mar 2, 2008]
- Fixed problem with negative folder size display for accounts with >2GB
- Fixed a problem where a certain type of error [Command failed: UID FETCH x (UID)] was being reported in the backup details, but not in the backup summary and was therefore easy to miss. The underlying failed UID fetches are happening intermitently, if you experience this problem please follow the instructions in this post to help resolve the issue.
- Fixed dataDir issue described in this post
- Disabled internal development logging (debug.log). Was enabled by mistake in previous release.
- Fixed a special case of restoring failure reported in this post (server reports the folder doesn't exist but refuses to create it with a "Mailbox exists" message).
