aboutsummaryrefslogtreecommitdiffstats
path: root/mail-client/mblaze/metadata.xml
blob: 09779ad946bb44c8074c6bf87af7d9d55e4d193c (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
  <upstream>
    <remote-id type="github">leahneukirchen/mblaze</remote-id>
  </upstream>
  <maintainer type="person">
    <name>la ninpre</name>
    <email>aaoth@aaoth.xyz</email>
  </maintainer>
  <longdescription>
    The mblaze message system is a set of Unix utilities for processing and
    interacting with mail messages which are stored in maildir folders.

    Its design is roughly inspired by MH, the RAND Message Handling System,
    but it is a complete implementation from scratch.

    mblaze is a classic command line MUA and has no features for receiving or
    transferring messages; you can operate on messages in a local maildir
    spool, or fetch your messages using fdm(1), getmail(1), offlineimap(1),
    or similar utilities, and send it using dma(8), msmtp(1), sendmail(8), as
    provided by OpenSMTPD, Postfix, or similar.

    mblaze operates directly on maildir folders and doesn't use its own
    caches or databases.  There is no setup needed for many uses.  All
    utilities have been written with performance in mind.  Enumeration of all
    messages in a maildir is avoided unless necessary, and then optimized to
    limit syscalls.  Parsing message metadata is optimized to limit I/O
    requests.  Initial operations on a large maildir may feel slow, but as
    soon as they are in the file system cache, everything is blazingly fast.
    The utilities are written to be memory efficient (i.e. not wasteful), but
    whole messages are assumed to fit into RAM easily (one at a time).
  </longdescription>
</pkgmetadata>