From 27ea308bfba9a9f18430ffd2b8841c359fa9d52f Mon Sep 17 00:00:00 2001 From: Oswald Buddenhagen Date: Sat, 17 Jan 2004 11:38:54 +0000 Subject: [PATCH] document mua interaction --- isync.1 | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/isync.1 b/isync.1 index 5068e33..0a6942f 100644 --- a/isync.1 +++ b/isync.1 @@ -277,6 +277,31 @@ the first \fBMailbox\fR command, and then leave out the \fBUser\fR command in the sections for each mailbox. \fBisync\fR will then use the global value by default. .. +.SH MAIL USER AGENT INTERACTION +To use \fBisync\fR effectively, you need a mail client that sets the T +(trashed) flag when it deletes a message from a maildir mailbox, instead of +just removing it altogether. Without such a client, \fBisync\fR will refetch the +locally deleted messages from the server since they will never get expunged. +Mutt (starting with version 1.3.27) is known to support this. Be sure to put +.IP "" 2 +set maildir_trash +.PP +in your ~/.muttrc when using Mutt. +.br +\fBisync\fR can be integrated into Mutt fairly easily with a few hooks: +.IP "" 2 +.nf +folder-hook ~A bind index $ +.br +folder-hook +\fImdir\fR 'macro index $ "!isync -e \fImdir\fR\\n"' +.fi +.PP +where \fImdir\fR is the name of the local mailbox (or its \fIalias\fR). +This works well so long as you are not modifying the IMAP mailbox outside of +Mutt. However, if you are using another mail program simultaneously Mutt +will have the wrong idea of the local mailbox flags and messages will start +disappearing from its index display (don't worry, they are still on disk). +.. .SH FILES .TP .B ~/.isyncrc