# HG changeset patch
# User Timo Sirainen <tss@iki.fi>
# Date 1032886342 -10800
# Node ID df941be7c6b09b762eb745cb1fd6b863d8ba72b4
# Parent  f5e59d65d12499d01ebb18c38f5fe14be60fd988
released 0.98.1

diff -r f5e59d65d124 -r df941be7c6b0 NEWS
--- a/NEWS	Tue Sep 24 19:39:00 2002 +0300
+++ b/NEWS	Tue Sep 24 19:52:22 2002 +0300
@@ -1,3 +1,9 @@
+v0.98.1 2002-09-24  Timo Sirainen <tss@iki.fi>
+
+	+ Faster and safer mbox rewriting when flags are updated
+	- Didn't save messages larger then 8192 bytes
+	- Several mbox breakages
+
 v0.98 2002-09-23  Timo Sirainen <tss@iki.fi>
 
 	+ mbox support is finally working. There's still some reliability
diff -r f5e59d65d124 -r df941be7c6b0 TODO
--- a/TODO	Tue Sep 24 19:39:00 2002 +0300
+++ b/TODO	Tue Sep 24 19:52:22 2002 +0300
@@ -36,10 +36,6 @@
        problems are:
          - we don't have a single open mbox fd, we open it multiple times
 	 - switching to exclusive lock may deadlock
-	 - because mbox-rewrite rename()s the file, the old file gets lost.
-	   if mailer only checks the fd lock, the new mails disappear..
-	   i guess the only way to fix this is to set dotlock before opening
-	   the mbox file.
      - maybe support Content-Length for figuring out size of text? at least
        mutt doesn't prefix "From " in outbox.. If we verify that both
        Content-Length and Lines match correctly, there's quite a little chance
@@ -48,9 +44,6 @@
        and now that we verify the From-line better, is this even needed?
      - rewriting could try to preserve the locations of fields it changes
        instead of writing them all to end..
-     - mbox-rewrite rename()s the file, which breaks if the original was a
-       symlink. but how do we fix this? we may not have write-access to the
-       directory where it points to, so we'd need to manually copy it..
      - empty lines at beginning of file still aren't ignored
  - read-only support for mailboxes where we don't have write-access? Maybe,
    but don't try to use their indexes since that's way too problematic, and
@@ -62,11 +55,8 @@
  - if .customflags is removed and Maildir files have custom flags, add
    "unknown1" "unknown2" etc. flags to .customflags file for each found flag
  - debug: index could be read-only mmaped when it's not locked. 
- - if message text is modified (or indexes are corrupted), this may happen:
-    Panic: file imap-bodystructure.c: line 179 (part_parse_headers):
-           assertion failed: (part->physical_pos >= inbuf->offset)
- - when index is being rebuilt, it always complains about hash/modifylog having
-   wrong indexid..
+ - when index is being rebuilt, it always complains about hash/modifylog
+   having wrong indexid..
 
 lib-storage:
  - support multiple mailbox formats and locations for one user. that would
@@ -99,8 +89,6 @@
  - maybe limit the length of custom flags? we don't really have a problem
    with them, but with mbox a long X-IMAPbase could break something.. Maybe
    configurable, default to 50 chars?
- - "APPEND invalid data {5}" - says "+ OK" and after that says it's invalid.
-   that "+ OK" shouldn't be sent by imap-parser if LITERAL_SIZE is used..
  - SEARCH should use imap-msgcache, especially for size checking
 
 general:
diff -r f5e59d65d124 -r df941be7c6b0 configure.in
--- a/configure.in	Tue Sep 24 19:39:00 2002 +0300
+++ b/configure.in	Tue Sep 24 19:52:22 2002 +0300
@@ -1,7 +1,7 @@
 AC_INIT(src)
 
 AM_CONFIG_HEADER(config.h)
-AM_INIT_AUTOMAKE(dovecot, 0.98)
+AM_INIT_AUTOMAKE(dovecot, 0.98.1)
 
 AM_MAINTAINER_MODE