1SUP-SYNC(1)                                                        SUP-SYNC(1)
2
3
4

NAME

6       sup-sync - sychronize the Sup index with message sources
7

SYNOPSIS

9       sup-sync [options] source ...
10

DESCRIPTION

12       Synchronizes  the  Sup index with one or more message sources by adding
13       messages, deleting messages, or changing message state in the index  as
14       appropriate.
15
16       “Message  state”  means read/unread, archived/inbox, starred/unstarred,
17       and all user-defined labels on each message.
18
19       “Default source state” refers to any state that  a  source  itself  has
20       keeps  about  a  message.  Sup-sync uses this information when adding a
21       new message to the index.  The source state  is  typically  limited  to
22       read/unread,  archived/inbox  status  and  a  single label based on the
23       source name.  Messages using the default source state are placed in the
24       inbox (i.e. not archived) and unstarred.
25
26       If no sources are given, sync from all usual sources.  Supported source
27       URI schemes can be seen by running “sup-add --help”.
28

MESSAGE STATE OPTIONS

30       --asis If the message is already in  the  index,  preserve  its  state.
31              Otherwise, use default source state (default)
32
33       --restore dumpfile
34              Restore  message  state  from a dump file created with sup-dump.
35              If a message is not in this dumpfile, act as --asis
36
37       --discard
38              Discard any message state in  the  index  and  use  the  default
39              source state.  Dangerous!
40
41       -x, -  When using the default source state, mark messages as archived.
42
43       -r, --read
44              When using the default source state, mark messages as read.
45
46       --extra-labels STRING
47              When  using  the default source state, also apply these user-de‐
48              fined labels (a comma-separated list) (default)
49

OTHER OPTIONS

51       -v, --verbose
52              Print message ids as they’re processed.
53
54       -o, --optimize
55              As the final operation, optimize the index.
56
57       --all-sources
58              Scan over all sources.
59
60       -n, --dry-run
61              Don’t actually modify the  index.   Probably  only  useful  with
62              --verbose.
63
64       --version
65              Show version information
66
67       -h, --help
68              Show help message
69

FILES

71       $HOME/.sup/sources.yaml
72              Configuration file for Sup mail sources
73

SEE ALSO

75       sup(1),    sup-add(1),   sup-config(1),   sup-dump(1),   sup-sync-back-
76       maildir(1), sup-tweak-labels(1)
77

REPORTING BUGS

79       You are welcome to submit bug reports to the Sup issue tracker, located
80       at
81
82       <https://github.com/sup-heliotrope/sup/issues>
83

CONTACT INFORMATION

85       The Sup web page:
86              <http://supmua.org/>
87
88       Code repository:
89              <https://github.com/sup-heliotrope/sup/>
90
91       Sup Wiki:
92              <https://github.com/sup-heliotrope/sup/wiki/>
93
94       Sup IRC channel:
95              #sup @ freenode.net
96
97       Mailing list:
98              supmua@googlegroups.com
99
100              supmua+subscribe@googlegroups.com
101
102              Archives: <https://groups.google.com/d/forum/supmua/>
103

105       Copyright © 2006-2009 William Morgan <mworgan-sup@masanjin.net>
106
107       Copyright @ 2013-2014 Sup developers
108
109       Permission  is  granted  to  copy  and distribute this manual under the
110       terms of the GNU General Public License; either version 2 or  (at  your
111       option) any later version.
112

AUTHORS

114       Sup was originally written by William Morgan <wmorgan-sup@masanjin.net>
115       and is now developed and maintained by the Sup developers.
116
117
118
119Sup User Manual                  April 9, 2012                     SUP-SYNC(1)
Impressum