mailsync-5.2.2/ 0000755 0000000 0000000 00000000000 12021470640 010221 5 ustar mailsync-5.2.2/CVS/ 0000755 0000000 0000000 00000000000 10340571361 010660 5 ustar mailsync-5.2.2/CVS/Entries 0000644 0000000 0000000 00000000715 10340571361 012217 0 ustar D/doc////
D/src////
D/acinclude////
/COPYING/1.1/Wed Jan 22 22:49:08 2003//
D/debian////
/AUTHORS/1.1/Fri Jan 24 09:45:04 2003//
/TODO/1.24/Wed Jun 9 20:58:07 2004//
/Makefile.am/1.6/Mon Jun 14 09:18:00 2004//
/README/1.14/Fri Jun 18 07:39:33 2004//
/.cvsignore/1.6/Fri Aug 20 08:08:13 2004//
/autogen.sh/1.4/Fri Aug 20 08:09:10 2004//
/configure.ac/1.18/Fri Aug 20 08:10:10 2004//
/THANKS/1.11/Tue Nov 22 10:26:58 2005//
/NEWS/1.32/Tue Nov 22 10:28:05 2005//
mailsync-5.2.2/CVS/Repository 0000644 0000000 0000000 00000000011 07614070512 012754 0 ustar mailsync
mailsync-5.2.2/CVS/Root 0000644 0000000 0000000 00000000057 07614070512 011532 0 ustar :ext:tpo@cvs.sourceforge.net:/cvsroot/mailsync
mailsync-5.2.2/doc/ 0000755 0000000 0000000 00000000000 10350351123 010763 5 ustar mailsync-5.2.2/doc/mail_open_close_flowchart.svg 0000644 0000000 0000000 00000104127 10063261420 016713 0 ustar
mailsync-5.2.2/doc/CVS/ 0000755 0000000 0000000 00000000000 10350351174 011424 5 ustar mailsync-5.2.2/doc/CVS/Entries 0000644 0000000 0000000 00000000511 10350351174 012755 0 ustar D/examples////
/ABSTRACT/1.1/Fri Sep 6 20:04:15 2002//
/mail_open_close_flowchart.dia/1.1/Mon Jun 14 09:12:05 2004/-kb/
/mail_open_close_flowchart.svg/1.1/Mon Jun 14 08:34:24 2004//
/mail_open_close_flowchart2.svg/1.1/Sun Jun 13 18:00:29 2004//
/HACKING/1.3/Wed Jun 30 08:12:01 2004//
/mailsync.1/1.8/Thu Dec 15 20:30:11 2005//
mailsync-5.2.2/doc/CVS/Repository 0000644 0000000 0000000 00000000015 07614073620 013530 0 ustar mailsync/doc
mailsync-5.2.2/doc/CVS/Root 0000644 0000000 0000000 00000000057 07614073620 012302 0 ustar :ext:tpo@cvs.sourceforge.net:/cvsroot/mailsync
mailsync-5.2.2/doc/mailsync.1 0000644 0000000 0000000 00000006315 10350351123 012671 0 ustar .\" Hey, EMACS: -*- nroff -*-
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH MAILSYNC 1 "February 15, 2003"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh disable hyphenation
.\" .hy enable hyphenation
.\" .ad l left justify
.\" .ad b justify to both left and right margins
.\" .nf disable filling
.\" .fi enable filling
.\" .br insert line break
.\" .sp insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
mailsync \- Synchronize IMAP mailboxes
.SH SYNOPSIS
.B mailsync
.RI [ options ] " channel"
.br
or
.br
.B mailsync
.RI [ options ] " store"
.br
or
.br
.B mailsync
.RI [ options ] " channel store"
.br
.SH DESCRIPTION
This manual page documents briefly the \fBmailsync\fB command.
.PP
.\" TeX users may be more comfortable with the \fB\fP and
.\" \fI\fP escape sequences to invode bold face and italics,
.\" respectively.
\fBmailsync\fP is a way of keeping a collection of mailboxes synchronized. The
mailboxes may be on the local filesystem or on an IMAP server.
There are three invocations of \fBmailsync\fP:
The first will synchronize two sets of mailboxes - in mailsync referred to
as "stores".
The second form will list the contents of a store. It's usage is recommended
before synchronizing two stores to check whether mailsync is seeing what you
are expecting it to see.
The third form will show you what has changed in a store since the last
sync.
.SH OPTIONS
A summary of options is included below.
.TP
.B \-f file
Use alternate config file.
.TP
.B \-n
Don't delete messages when synchronizing.
.TP
.B \-D
Delete any empty mailboxes after synchronizing..
.TP
.B \-m
Show from, subject, etc. of messages that are killed or moved when synchronzing.
.TP
.B \-M
Also show message-ids (turns on \fB\-m\fP).
.TP
.B \-s
Says what would be done without doing it (turns on \fB\-n\fP).
Attention: this \fBwill\fP change the "Seen" flag of emails and will create new,
empty mailboxes in order to be able to compare them.
.TP
.B \-v
Show IMAP chatter.
.TP
.B \-vb
Show warning about braindammaged message ids
.TP
.B \-vw
Show warnings
.TP
.B \-vp
Show RFC 822 mail parsing errors
.TP
.B \-h
Show help.
.TP
.B \-d
Show debug info.
.B \-di
Debug/log IMAP protocol telemetry.
.B \-dc
Debug config.
.TP
.B \-t mid
Use mailsync with specified message-id algorithm. Currently you have the
choice between \fBmd5\fP and \fBmsgid\fP (default). \fBmsgid\fP uses the
Message-ID in the mail header to identify a message. \fBmd5\fP calculates
a MD5 hash from the "From", "To", "Subject", "Date" and "Message-ID" headers
and uses that as message identifier.
If you use mailclients and servers that allow empty Message-IDs (f.ex. in mail
drafts) then you should use the md5 algorithm.
.SH SEE ALSO
There is more documentation in
.IR /usr/share/doc/mailsync
, and in
.IR /usr/share/doc/libc-clientxxxxxx/internal.txt
.SH AUTHOR
Originally written by Jaldhar H. Vyas for the Debian
GNU/Linux system. Updates by T. Pospisek .
mailsync-5.2.2/doc/ABSTRACT 0000644 0000000 0000000 00000003114 07536205077 012132 0 ustar Mailsync is a way of synchronizing a collection of mailboxes. The
algorithm is a 3-way diff. Two mailboxes are simultaneously compared
to a record of the state of both mailboxes at last sync. New messages
and message deletions are propagated between the two mailboxes. If
you're familiar with CVS, it's the same principle, except there's no
opportunity for conflicts.
Mailsync can be used for many things. I wrote it for synchronizing
my desktop mail with my laptop. You can also use it if your mail is
kept on an IMAP server, but your favorite mail client doesn't totally
grok IMAP---for instance, I use VM under Emacs, and VM keeps a copy of
my mail in my home directory, and I synchronize that with the IMAP
server. You can keep your mail in arbitrarily many places and keep it
all consistent.
Mailsync is based on the "c-client" library developed at the
University of Washington. C-client was designed for writing IMAP
clients, but it also can access local mailbox files in many formats,
with a nearly consistent API. Mailsync's mailboxes can be on IMAP
servers, on the local filesystem in UNIX, MH, or any other format
c-client supports.
What about "detached client" mode in an IMAP client? Mailsync
attempts to solve the same problem in a different way. The "detached
client" idea assumes that there's a master server and a
periodically-connected client. Mailsync does not designate a server
or a client. (In fact, it acts sort of like a client that arbitrates
between two servers.)
Currently, the concept of message identity is based entirely on the
Message-ID field. This may change.
mailsync-5.2.2/doc/mail_open_close_flowchart2.svg 0000644 0000000 0000000 00000024413 10063113075 016776 0 ustar
mailsync-5.2.2/doc/mail_open_close_flowchart.dia 0000644 0000000 0000000 00000017330 10063265745 016666 0 ustar ]o ]0} )8x~h'"mxgg(y9HҕW7mgixgo_2B_fb2z_^bZיVo_~Xn}Ǐdy2ܒiozY*?Wv5f˳?Wew>˯.ßoǼxΎgW8O\Gߌۏ/'~ͣ-5ρ?SZMA~U|ϪDVj2{L7r$ILI,ILb'd8Vq{:|Ef+/'|̧&?;=ībAQՇѧ]_%V<3,'gq٪^?soDOUwʿ\{DmsO͓>ַ5bmp 1?rYK[
7