diff options
| -rw-r--r-- | archivemail.1 | 7 | ||||
| -rw-r--r-- | archivemail.sgml | 8 |
2 files changed, 15 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 diff --git a/archivemail.sgml b/archivemail.sgml index 3ce582e..065a5f3 100644 --- a/archivemail.sgml +++ b/archivemail.sgml @@ -415,6 +415,14 @@ There is no way around this, it's just how <application/IMAP/ works. This does not apply, however, if you run <command/archivemail/ with the options <option/--dry-run/ or <option/--copy/. </Para> +<Para> +<command/archivemail/ relies on server-side searches to determine the messages +that should be archived. +When matching dates, <application/IMAP/ servers refer to server internal message +dates, and these may differ from both delivery time and the message's +<application/Date/ header. +Also, there exist broken servers which do not implement server side searches. +</Para> <RefSect3><Title><acronym/IMAP/ <acronym/URLs/</Title> <Para> <command/archivemail/'s <application/IMAP/ <acronym/URL/ parser was written |