Go to file
2016-07-29 17:07:25 +02:00
contrib add contrib/malternative 2016-07-29 15:57:02 +02:00
man mshow: hard-code simple multipart/alternative policy 2016-07-29 17:07:25 +02:00
blaze822_priv.h import musl memmem 2016-07-26 18:10:39 +02:00
blaze822.c blaze822: blaze822_file: allocate enough space for read 2016-07-29 15:41:41 +02:00
blaze822.h mshow: actually filter the parts 2016-07-29 15:15:57 +02:00
COPYING COPYING: add mpick 2016-07-28 17:54:08 +02:00
filter.c mshow: actually filter the parts 2016-07-29 15:15:57 +02:00
filter.example filter.example: use $PIPE_CHARSET for lynx 2016-07-20 14:49:01 +02:00
maddr.c maddr: add usage 2016-07-26 21:59:25 +02:00
Makefile mshow: actually filter the parts 2016-07-29 15:15:57 +02:00
mcomp mrepl: reply-all by default, respect reply-to 2016-07-28 13:23:36 +02:00
mdeliver.c mdeliver: add usage 2016-07-26 21:59:25 +02:00
mdirs.c mdirs: add usage 2016-07-26 21:59:25 +02:00
mflag.c mflag: add usage 2016-07-26 21:59:25 +02:00
mhdr.c mhdr: typo 2016-07-28 13:48:17 +02:00
minc.c minc: add usage 2016-07-26 21:59:26 +02:00
mless mless: R to toggle raw message 2016-07-29 12:54:03 +02:00
mlesskey.example mless: R to toggle raw message 2016-07-29 12:54:03 +02:00
mlist.c mlist: add usage 2016-07-26 21:59:26 +02:00
mmime.c mmime: delete dead store 2016-07-26 00:35:59 +02:00
mnext add mprev/mnext to call mless with appropriate offset 2016-07-20 15:43:53 +02:00
mpick.c mpick: fixes 2016-07-29 04:31:34 +02:00
mprev add mprev/mnext to call mless with appropriate offset 2016-07-20 15:43:53 +02:00
mrepl add mrepl 2016-07-20 16:58:37 +02:00
mscan.c mscan: keep local time 2016-07-28 12:20:23 +02:00
mseq.c mseq: deal with indentation in -C 2016-07-28 13:49:00 +02:00
mshow.c mshow: hard-code simple multipart/alternative policy 2016-07-29 17:07:25 +02:00
msort.c msort: check realloc 2016-07-29 13:10:25 +02:00
mthread.c mthread: add usage 2016-07-26 22:09:26 +02:00
mymemmem.c import musl memmem 2016-07-26 18:10:39 +02:00
mystrverscmp.c mystrverscmp: fix include 2016-07-26 18:30:54 +02:00
README README: update 2016-07-28 18:09:31 +02:00
rfc2045.c rfc2045: relax MIME check 2016-07-29 16:41:45 +02:00
rfc2047.c rfc2047: blaze822_decode_qp: skip =CRLF 2016-07-29 13:58:11 +02:00
seq.c seq: blaze822_seq_next: fix mseq -n . 2016-07-28 23:10:32 +02:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

MINTRO(7)              Miscellaneous Information Manual              MINTRO(7)

NAME
     mintro  Santoku introduction

DESCRIPTION
     The Santoku message system is a set of Unix utilities to deal with mail
     kept in Maildir folders.

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

     Santoku consists of a set of Unix tools that each do one job:
     maddr(1)     to extract addresses from mail
     mcomp(1)     to write and send mail
     mdeliver(1)  to deliver messages or import mailboxes
     mdirs(1)     to find Maildirs
     mflag(1)     to change flags (marks) of mail
     mhdr(1)      to extract mail headers
     minc(1)      to incorporate new mail
     mless(1)     to conveniently read mail in less(1)
     mlist(1)     to list and filter mail messages
     mmime(1)     to create MIME messages
     mpick(1)     to filter mail
     mrepl(1)     to reply to mail
     mscan(1)     to generate single line summaries of mail
     mseq(1)      to manipulate mail sequences
     mshow(1)     to render mail and extract attachments
     msort(1)     to sort mail
     mthread(1)   to arrange mail into discussions

PRINCIPLES
     Santoku is a classic command line MUA with 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.  Santoku expects your mail to reside in Maildir folders.

     Santoku 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).

     Santoku 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 nor desirable).  There may be issues with very old,
     nonconforming, messages.

     Santoku is written in portable C, using only POSIX functions (apart from
     a tiny Linux-only optimization).  It supports MIME and more than 7-bit
     messages (everything the host iconv(3) can decode).  It assumes you work
     in a UTF-8 environment.  Santoku works well together with other Unix mail
     tools such as offlineimap(1), mairix(1), or mu(1).

EXAMPLES
     Santoku tools are designed to be composed together into a pipe.  It is
     suitable for interactive use and for scripting.  It integrates well into
     a Unix workflow.

     For example, you could decide you want to look at all unseen mail in your
     INBOX, oldest first.
           mlist -s ~/Maildir/INBOX | msort -d | mscan
     To operate on a set of mails in multiple steps, you can save a list of
     mail as a sequence.  E.g. add a call to mseq -S to above command:
           mlist -s ~/Maildir/INBOX | msort -d | mseq -S | mscan
     Now mscan will show message numbers and you could look at the first five
     mails at once, for example:
           mshow 1:5
     Likewise, you could decide to look at all freshly received mail in all
     folders, thread it and look at it interactively:
           mdirs ~/Maildir | xargs minc | mthread | mless
     Or you could look at the attachments of the 20 largest mails in your
     INBOX:
           mlist ~/Maildir/INBOX | msort -s | tail -20 | mshow -t
     Or apply the patches from the current mail:
           mshow -O. '*.diff' | patch
     As usual with pipes, the sky is the limit.

CONCEPTS
     Santoku deals with messages (which are files), folders (which are Maildir
     folders), sequences (which are newline-separated lists of messages,
     possibly persisted on disk in ~/.santoku/seq), and the current message
     (kept as a symlink in ~/.santoku/cur).

     Messages in the persisted sequence can be referred to using special
     syntax as explained in mmsg(7).

     Many utilities have a default behavior when used interactively from a
     terminal (e.g. operate on the current message or the current sequence).
     For scripting, you must make these arguments explicit.

SEE ALSO
     mailx(1), nmh(7)

AUTHORS
     Christian Neukirchen <chneukirchen@gmail.com>

LICENSE
     Santoku is in the public domain.

     To the extent possible under law, the creator of this work has waived all
     copyright and related or neighboring rights to this work.

     http://creativecommons.org/publicdomain/zero/1.0/

Void Linux                       July 22, 2016                      Void Linux