mblaze

Unix utilities to deal with Maildir - my mirror
git clone https://pi.duncano.de/git/mblaze.git
Log | Files | Refs | README | COPYING

commit fb8674ef104a117dd33e7f2365a06e75c3016e82
parent 1cdb871e3d791138abcce148e1c4c619ff1d95fc
Author: Christian Neukirchen <chneukirchen@gmail.com>
Date:   Mon,  5 Sep 2016 12:54:07 +0200

README: update

Diffstat:
README | 18+++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/README b/README @@ -40,15 +40,15 @@ PRINCIPLES it using sendmail(8), as provided by OpenSMTPD, Postfix, msmtp(1), dma(8) or similar. mblaze expects your mail to reside in Maildir folders. - mblaze operates directly on Maildir and doesn't use caches or database. - There is no setup needed for many uses. All tools have been written with - performance in mind. Enumeration of all mails in a Maildir is avoided - unless necessary, and then optimized to use few syscalls. Parsing mail - metadata is optimized to use few I/O requests. Initial operations on big - Maildir may feel slow, but as soon as they are in cache, everything is - blazing fast. The tools are written to be memory efficient (i.e. not - wasteful), but whole messages are assumed to fit into RAM easily (at a - time). + mblaze operates directly on Maildir and doesn't use own caches or + databases. There is no setup needed for many uses. All tools have been + written with performance in mind. Enumeration of all mails in a Maildir + is avoided unless necessary, and then optimized to use few syscalls. + Parsing mail metadata is optimized to use few I/O requests. Initial + operations on big Maildir may feel slow, but as soon as they are in file + system cache, everything is blazing fast. The tools are written to be + memory efficient (i.e. not wasteful), but whole messages are assumed to + fit into RAM easily (at a time). mblaze has been written from scratch and tested on a big pile of personal mail, but is not actually 100% RFC conforming (which is neither worth it