|
|
|
@ -8,9 +8,9 @@ DESCRIPTION
|
|
|
|
|
kept in Maildir folders.
|
|
|
|
|
|
|
|
|
|
Its design is roughly inspired by MH, the RAND Message Handling System,
|
|
|
|
|
but its is a complete implementation from scratch.
|
|
|
|
|
but it is a complete implementation from scratch.
|
|
|
|
|
|
|
|
|
|
mblaze consists of a set of Unix tools that each do one job:
|
|
|
|
|
mblaze consists of these Unix tools that each do one job:
|
|
|
|
|
maddr(1) to extract addresses from mail
|
|
|
|
|
magrep(1) to find mails matching a pattern
|
|
|
|
|
mcom(1) to write and send mail
|
|
|
|
@ -34,8 +34,8 @@ DESCRIPTION
|
|
|
|
|
mthread(1) to arrange mail into discussions
|
|
|
|
|
|
|
|
|
|
PRINCIPLES
|
|
|
|
|
mblaze is a classic command line MUA with no features related to
|
|
|
|
|
receiving and transferring mail. You are expected to fetch your mail
|
|
|
|
|
mblaze is a classic command line MUA and has no features related to
|
|
|
|
|
receiving and transferring mail; you are expected to fetch your mail
|
|
|
|
|
using offlineimap(1), fdm(1), procmail(1), getmail(1) or similar and send
|
|
|
|
|
it using sendmail(8), as provided by OpenSMTPD, Postfix, msmtp(1), dma(8)
|
|
|
|
|
or similar. mblaze expects your mail to reside in Maildir folders.
|
|
|
|
@ -48,7 +48,7 @@ PRINCIPLES
|
|
|
|
|
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).
|
|
|
|
|
fit into RAM easily (one 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
|
|
|
|
|