aboutsummaryrefslogtreecommitdiffstats
path: root/archivemail.1
diff options
context:
space:
mode:
authorNikolaus Schulz <microschulz@web.de>2007-11-02 20:42:16 +0000
committerNikolaus Schulz <microschulz@web.de>2007-11-02 20:42:16 +0000
commitc5002cdefbc5fd723c20fa483ec8885de894effe (patch)
treee6d6a3e7842d27148dd8bc5347aa7c5283ef60d6 /archivemail.1
parentc97b10f253363f719db7f3734522e086ddd7d275 (diff)
downloadarchivemail-c5002cdefbc5fd723c20fa483ec8885de894effe.tar.gz
archivemail-c5002cdefbc5fd723c20fa483ec8885de894effe.tar.bz2
archivemail-c5002cdefbc5fd723c20fa483ec8885de894effe.zip
Updated manpage: note that IMAP server internal message dates may differ from
user-visible date headers, and that there exist servers not supporting searches.
Diffstat (limited to 'archivemail.1')
-rw-r--r--archivemail.17
1 files changed, 7 insertions, 0 deletions
diff --git a/archivemail.1 b/archivemail.1
index 55d2543..e63d326 100644
--- a/archivemail.1
+++ b/archivemail.1
@@ -267,6 +267,13 @@ probably not show up as 'new' in your user agent later on.
There is no way around this, it's just how \fBIMAP\fR works.
This does not apply, however, if you run \fBarchivemail\fR with the options
\fB--dry-run\fR or \fB--copy\fR\&.
+.PP
+\fBarchivemail\fR relies on server-side searches to determine the messages
+that should be archived.
+When matching dates, \fBIMAP\fR servers refer to server internal message
+dates, and these may differ from both delivery time and the message's
+\fBDate\fR header.
+Also, there exist broken servers which do not implement server side searches.
.SS "IMAP URLS"
.PP
\fBarchivemail\fR\&'s \fBIMAP\fR URL parser was written