2011-05-25 21:04:13 +02:00
|
|
|
.TH MU CLEANUP 1 "May 2011" "User Manuals"
|
2010-08-15 19:29:15 +02:00
|
|
|
|
|
|
|
|
.SH NAME
|
|
|
|
|
|
|
|
|
|
mu cleanup \- clean up the mu database
|
|
|
|
|
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
|
|
|
|
|
|
.B mu cleanup [options]
|
|
|
|
|
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
|
2011-04-05 06:34:22 +02:00
|
|
|
\fBcleanup\fR removes messages from the database for which no corresponding
|
|
|
|
|
file can be found in the file system. This is done automatically when running
|
|
|
|
|
\fBmu index\fR (unless \fB\-\-nocleanup\fR was specified), but \fBmu cleanup\fR
|
2011-05-25 21:04:13 +02:00
|
|
|
can be used to do the cleanup explicitly.
|
2010-08-15 19:29:15 +02:00
|
|
|
|
2010-10-25 23:25:14 +02:00
|
|
|
\fBmu cleanup\fR does not remove messages that are outside the currently
|
2010-11-30 21:11:40 +01:00
|
|
|
specified Maildir, as long as they still exist. The command only takes global
|
|
|
|
|
options, which are described in the \fBmu (1)\fR man page.
|
2010-08-15 19:29:15 +02:00
|
|
|
|
2011-01-12 22:14:51 +01:00
|
|
|
.SH RETURN VALUE
|
|
|
|
|
|
|
|
|
|
\fBmu cleanup\fR return 0 upon successful completion. Anything else leads to a
|
|
|
|
|
non-zero return value, for example:
|
|
|
|
|
|
2011-05-25 21:04:13 +02:00
|
|
|
.nf
|
2011-01-12 22:14:51 +01:00
|
|
|
| code | meaning |
|
|
|
|
|
|------+--------------------------------|
|
|
|
|
|
| 0 | ok |
|
|
|
|
|
| 1 | general error |
|
|
|
|
|
| 4 | database is corrupted |
|
2011-05-25 21:04:13 +02:00
|
|
|
.fi
|
2011-01-12 22:14:51 +01:00
|
|
|
|
2010-08-15 19:29:15 +02:00
|
|
|
.SH BUGS
|
|
|
|
|
|
2010-09-05 20:20:46 +02:00
|
|
|
Please report bugs if you find them:
|
2010-08-15 19:29:15 +02:00
|
|
|
.BR http://code.google.com/p/mu0/issues/list
|
|
|
|
|
|
|
|
|
|
.SH AUTHOR
|
|
|
|
|
|
|
|
|
|
Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>
|
|
|
|
|
|
|
|
|
|
.SH "SEE ALSO"
|
|
|
|
|
|
2011-05-25 21:04:13 +02:00
|
|
|
.BR maildir(5)
|
|
|
|
|
.BR mu-index(1)
|
|
|
|
|
.BR mu(1)
|
