Mercurial > dovecot > original-hg > dovecot-1.2
annotate TODO @ 6524:20a5e69e6266 HEAD
Added tag 1.1.beta2 for changeset 19b73ae1d6f6
| author | Timo Sirainen <tss@iki.fi> |
|---|---|
| date | Sun, 30 Sep 2007 23:21:18 +0300 |
| parents | 31f374bcbd31 |
| children | c0d18ea33806 |
| rev | line source |
|---|---|
| 6402 | 1 - message-header-decode.c: handle decoding errors by fallbacking to simply |
| 2 returning the data as ASCII (the whole thing, beginning from =?) | |
| 3 - dbox: clean up temp.* files once in a while | |
| 4 - write first extension intros in dovecot.index.log always with names | |
| 5 - Panic: file mail-index-view-sync.c: line 297 (mail_index_view_sync_begin): assertion failed: (view->index->map->hdr.messages_count >= ctx->finish_min_msg_count) | |
| 6 - after index reset | |
| 7 - cache compressions aren't handled exactly right. especially when creating | |
| 8 the initial cache file other processes seem to give cache corruption errors. | |
| 9 - don't delay IDLE changes too long? | |
| 10 - expunged messages' flags may get updated in views where they're not yet | |
| 11 expunged (e.g. "expunge uid 2", "+flags \seen uid 1:3") | |
| 12 - POP3 UIDL caching | |
| 13 - Cydir/dbox doesn't respect LIST RETURN (CHILDREN) | |
| 6232 | 14 - SORT: Invalid input is supposed to be sorted last. |
| 6105 | 15 - indexes: are cache prev_offsets updated right? |
| 16 - mmap_disable: updated cache header doesn't invalidate other processes' cache? | |
| 5621 | 17 |
| 6105 | 18 - maildir+pop3/deliver fast updates: |
| 19 - with locking enabled, pop3 could just keep the one and same sync lock and | |
| 20 do the whole thing using sync transaction | |
| 21 - don't update dovecot-uidlist if dovecot.index.cache doesn't exist / | |
| 22 there's nothing to cache | |
| 23 - if all messages are expunged and there are no unknown extensions in index, | |
| 24 unlink dovecot.index and rotate log and add some initial useful info to | |
| 25 the log (uidvalidity, nextuid) | |
| 5621 | 26 |
| 6105 | 27 - maildir |
| 28 - physical separator could be configurable | |
| 29 - setting flags to same as they already are causes unnecessary | |
| 30 rename()s with identical parameters | |
| 31 - deliver+maildir: if new mails are in new/ or cur/ they're not added to | |
| 32 dovecot-uidlist but newly saved mails are, so UIDs will be in wrong order | |
| 33 - maildir_copy_with_hardlinks: We're currently first hardlinking to tmp/ and | |
| 34 then rename()ing. This wouldn't be necessary if uidlist syncing noticed | |
| 35 that someone else already had added them to uidlist, and the existing UIDs | |
| 36 could be assigned to them in the index. | |
| 37 - maildir_copy_preserve_filename=yes has a race condition causing "Append with | |
| 38 UID n, but next_uid = y" errors when quota plugin is loaded. Practically | |
| 39 won't happen except in stress testing. | |
| 5621 | 40 |
| 6105 | 41 - mbox |
| 42 - UID renumbering doesn't really work after all? | |
| 43 - still problems with CRLF mboxes.. | |
| 44 | |
| 45 - Mailbox list indexes | |
| 46 - Should probably check dovecot.index.log stamp/size too so that non-zero | |
| 47 recent counters get reset | |
| 48 - Why are updates so slow? | |
| 49 - Support for FS layout | |
| 50 | |
| 5557 | 51 - don't use squat with header if index doesn't exist |
| 52 - don't use squat index if searching only a couple of mails | |
| 53 - threading: (all done?) | |
| 54 - duplicate: mark original as rebuild | |
| 55 - re-parent (also reparenting to root): mark as rebuild | |
| 56 - unref: if refcount drops to zero, set children's parent=0 (can happen | |
| 57 if there are only grandchildren and dummy children) | |
| 58 - mail-hash: stat() and reopen if needed | |
| 59 - subjects: group roots togethere already while gathering subjects. then | |
| 60 go through them and sort them to get their sent date. then start writing | |
| 61 the nodes out. sorting needs to these cases: | |
| 62 1) root is dummy -> just sort their children. if there are dummies | |
| 63 they're skipped and their children ascend | |
| 64 2) root is non-dummy -> there are no dummies at all in the thread. | |
| 65 the root has the oldest date in the thread. after the root if there | |
| 66 are re: or fwd: messages they're children to the root. if there are | |
| 67 more messages after that, a new dummy parent needs to be created, | |
| 68 and the rest of the messages need to be sorted before sending | |
| 69 | |
| 6105 | 70 - mail_log: log appends |
| 71 - pop3 proxying(?): dovecot: login: tried to change state 2 -> 2 | |
| 72 - logging consistency: | |
| 73 http://www.dovecot.org/list/dovecot/2007-April/021532.html | |
| 74 - EXPUNGE command in read-only mailbox should give an error message if | |
| 75 there are messages marked as \Deleted? | |
| 76 - dovecot -o setting=something overriding | |
| 5557 | 77 - file_cache: we're growing the mmap in page size blocks, which is horribly |
| 78 slow if mremap() doesn't exist. | |
| 79 - login_max_processes_count shouldn't count proxying processes | |
| 80 | |
| 81 - Allow %variables in mail_chroot setting | |
| 82 - something should be done to umask setting. we should be creating files with | |
| 83 0666 or 0777 and rely on umask, but we shouldn't do that unless we're sure | |
| 84 that the umask is the wanted one (ie. imap/pop3 process wasn't started | |
| 85 directly) | |
| 86 - ssl_verify_client_cert isn't working if the SSL cert doesn't have CRL | |
| 87 | |
| 3087 | 88 - keywords: |
| 89 - add some limits to how many there can be | |
| 90 - don't return \* in PERMANENTFLAGS when we're full | |
| 91 - remove unused keywords? | |
| 2774 | 92 |
| 93 - caching | |
| 3904 | 94 - force bits should be used only for nonregistered fields |
| 95 - change envelope parsing not to use get_headers() so imap.envelope can | |
| 96 actually be cached without all the headers.. | |
| 6105 | 97 - if there's no other pressure for compression, we should do it when |
| 98 enough temp fields are ready to be dropped | |
| 3904 | 99 - we could try compressing same field values into a single |
| 100 location in cache file. | |
| 101 - support caching all message headers. this could be useful when | |
| 102 indexes are in local disk but actual mails are accessed through NFS. | |
| 2774 | 103 |
| 3087 | 104 - mbox |
| 4449 | 105 - dirty state should be stored to index (with mbox_very_dirty_syncs) |
| 106 - after some locking timeouts: mbox-lock.c: line 518 (mbox_lock): | |
| 107 assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) | |
| 108 - controldir for mboxes too and place subscriptions file there? | |
| 3904 | 109 - syncing existing indexes takes 4x longer than creating new one, why? |
| 110 - how well does dirty sync + status work? it reads the last mail every | |
| 111 time? not very good.. | |
| 112 - always add empty line. make the parser require it too? syncing should | |
| 113 make sure there always exists two LFs at end of file. raw-mbox-stream | |
| 114 should make sure the last message ends with LF even if it doesn't exist | |
| 115 in the file | |
| 116 - Quote "From ", unquote ">From " | |
| 4449 | 117 - COPY doesn't work to itself (lock assert crash, for now just disallowed) |
| 2143 | 118 - if we can't create dotlock file for mbox, make sure it still can be |
| 119 selected in read-only state | |
| 120 | |
| 4449 | 121 - dbox |
| 122 - keyword list header locking isn't correct now. saving uses file's | |
| 5557 | 123 dotlock, sync uses sync lock. and what about reading?... (I think this |
| 124 is fixed?) | |
| 4449 | 125 - append_offset in header shouldn't be trusted |
| 126 - show in index if there are expunge-flagged mails in the mailbox | |
| 127 - pop3_lock_session doesn't work | |
| 3087 | 128 |
| 2143 | 129 - index |
| 130 - if log file is lost, generate it from old and new index | |
| 3087 | 131 - read-only support for mailboxes where we don't have write-access |
| 6105 | 132 - index file format changes: |
| 133 - pack UIDs to beginning of file with UID ranges | |
| 134 - use squat-like compressed uid ranges everywhere | |
| 2143 | 135 |
| 4449 | 136 - namespaces |
| 137 - namespaces: add new "auto_disable" flag so if the mailbox can't be opened | |
| 138 (eg. file doesn't exist), just ignore the problem and disable the | |
| 139 namespace | |
| 5621 | 140 - namespaces don't work in plugins: convert |
| 3087 | 141 - subscriptions file should contain namespace prefixes. at least optionally. |
| 142 there's the subscriptions = yes setting now for namespaces.. do it so that | |
| 143 if prefix = "" has subscriptions, it contains prefixes. otherwise not. | |
| 4128 | 144 - for shared/public namespaces default to "no" |
| 4449 | 145 |
| 146 - lib-storage | |
| 5557 | 147 - rename: allow moving between storages, as long as they're of same type |
| 4449 | 148 - x search charset asdf all -> should fail |
| 3087 | 149 - should we allow following symlinks in mbox/maildirs? they are now. |
| 150 - if we implement shared mailboxes with shared indexes, never do that or | |
| 151 others could symlink your personal mailboxes and see the indexes | |
| 152 created for it which may contain envelope etc. data | |
| 153 - this allows circular mailbox hierarchies which should be prevented by | |
| 154 eg. allowing max. 20 hierarchies. | |
| 155 | |
| 156 - login | |
| 4449 | 157 - when pipelining login command + post-login commands, login process should |
| 158 pass the command to imap/pop3 process (at least one pop3 client does this) | |
| 159 - imap-login: Master sent reply with unknown tag 1. client closed | |
| 160 connection at the exact same time master was logging it in? | |
| 161 see master_request_abort() | |
| 3087 | 162 - Digest-MD5: support integrity protection, and maybe crypting. Do it |
| 163 through login process like SSL is done? | |
| 164 - x login foo bar | |
| 165 x NO Authentication failed. | |
| 166 x login cras pass | |
| 167 * BYE Disconnected for inactivity. | |
| 168 ^ but it's not disconnecting! (buggy dovecot-auth not replying) | |
| 3744 | 169 probably because userdb lookup didn't reply, and fd was already sent |
| 170 for master.. should imap-login be handling it anymore?.. | |
| 3087 | 171 - imap-login: Authenticate PLAIN failed: Authentication failed: |
| 172 Authentication server isn't connected, try again later.. [127.0.0.1] | |
| 173 ^ NO Authentication failed. (should be Temporary login failure!) | |
| 174 - if auth process dies, login process should retry authentication if | |
| 175 possible. or if not, disconnect the client so it doesn't think the auth | |
| 176 failed. | |
| 177 - send client IP immediately after accept() to master process. make sure | |
| 178 master shows the IP if login dies unexpectedly. master should probably | |
| 179 also kill the login process if it doesn't kill itself soon enough.. or | |
| 180 maybe just log the IP immediately. | |
| 474 | 181 |
| 3087 | 182 - auth |
| 4449 | 183 - with blocking passdb we're not caching lookups if the password was wrong |
| 5557 | 184 - non-plaintext authentication doesn't support all features: |
| 185 - multiple passdbs don't work, only the first one is used | |
| 186 - auth cache's last_success password change check doesn't exist | |
| 3087 | 187 - remove system_user and allow returning multiple gids instead. |
| 188 - SIGHUP restarts auth processes .. but does it wait until they've finished | |
| 189 with all requests? no. | |
| 190 - does dovecot-auth really break when it runs out of fds? | |
| 4449 | 191 - dovecot-auth should limit how fast authentication requests are allowed |
| 192 from login processes. especially if there's one login/connection the speed | |
| 3087 | 193 should be something like once/sec. also limit how fast to accept new |
| 194 connections. | |
| 195 - support read-only logins. user could with alternative password get only | |
| 196 read-access to mails so mails could be read relatively safely with | |
| 197 untrusted computers. Maybe always send [ALERT] about the previous | |
| 198 read-only login time with IP? | |
| 4449 | 199 - dovecot-auth workers: create a separate dovecot-pam worker which shares |
| 200 pretty much all code with dovecot-auth worker but isn't linked against | |
| 201 any libraries. or..? this might be difficult to do, especially because the | |
| 202 workers currently can handle any kind of passdb/userb requests. perhaps | |
| 203 there should be a completely separate simple PAM authenticator binary. | |
| 526 | 204 |
| 3087 | 205 - master |
| 206 - configurable syslog prefix | |
| 3450 | 207 - if there are duplicate settings, complain about it |
| 3087 | 208 |
| 209 - quota | |
| 210 - if dovecot-uidlist can't be written, assume the new mails have UIDs | |
| 211 beginning from uidlist.next_uid. Whenever mails are expunged, overwrite | |
| 212 the next_uid field with the current highest next_uid. Whenever we have | |
| 213 assumed UIDs and uidlist gets updated, throw the client out with | |
| 214 "inconsist mailbox". | |
| 215 | |
| 216 - ssl | |
| 217 - add setting: ssl_options = bitmask. by default we enable all openssl | |
| 218 workarounds, this could be used to disable some of them | |
| 219 - gnutls support isn't working | |
| 965 | 220 |
| 3087 | 221 - search |
| 6232 | 222 - message header search: we should ignore LWSP between two MIME blocks(?) |
| 223 - message_search_init() could accept multiple search keywords so we | |
| 1250 | 224 wouldn't need to call it separately for each one (so we wouldn't need |
| 225 to parse the message multiple times). | |
| 226 - could optionally support scanning inside file attachments and use | |
| 227 plugins to extract text out of them (word, excel, pdf, etc. etc.) | |
| 228 - Create our own extension: When searching with TEXT/BODY, return | |
| 229 the message text surrounding the keywords just like web search engines | |
| 230 do. like: SEARCH X-PRINT-MATCHES TEXT "hello" -> * SEARCH 1 "He said: | |
| 231 Hello world!" 2 "Hello, I'm ...". This would be especially useful with | |
| 232 the above attachment scanning. | |
| 0 | 233 |
| 4449 | 234 - deliver |
| 5557 | 235 - recipient_delimiter setting so user+mailbox@domain works directly |
| 4449 | 236 |
| 3087 | 237 - general |
| 4449 | 238 - stop using atol(), atoi(), strtoul() etc. in places where we actually |
| 239 care about what they return, and rather create our own function which | |
| 240 checks if the input overflows the integer, and if so call i_fatal() | |
| 3087 | 241 - rfc2231 continuation support (useless?) |
| 1553 | 242 - rfc2557 support for BODYSTRUCTURE, as specified by RFC3501 |
| 4449 | 243 - LMTP server |
| 244 - ability to build plugins statically into the binaries | |
| 3087 | 245 - ~/.dovecotrc to override system wide settings. namespace settings should |
| 246 override all the previous namespace settings instead of adding new. | |
| 247 - things break if next_uid gets to 2^32 | |
|
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
248 |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
249 capabilities: |
| 4449 | 250 - preferrably all should be implemented as plugins |
|
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
251 - possibility to disable them from config file |
| 3087 | 252 - THREAD=ORDEREDSUBJECT - although pretty useless I'd think. |
| 5621 | 253 - acl (rfc4314) |
|
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
254 - id (rfc2971) |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
255 - must be configurable what gets sent, default to only name=Dovecot |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
256 - separate pre/post-login settings |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
257 - optionally log configured parts of the client information, but only |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
258 once, probably at the same time as logging "Logged in", |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
259 "Disconnected", etc. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
260 - remember to force truncating values longer than 30 chars, |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
261 especially before logging |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
262 - mailbox-referrals (rfc2193) |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
263 - this is useful whenever we would otherwise need to make the |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
264 connection ourself. for example load balancing and shared mailboxes |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
265 requiring another UID to run. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
266 - this rfc defines no exact way for server to detect if client |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
267 supports referrals or not. I don't think there's much point in |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
268 supporting only referrals, as most clients don't support them. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
269 Instead we should return referrals when we know that client |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
270 supports them, otherwise do the connecting ourself. If client |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
271 issues RLIST or RLSUB command, it's safe to assume it supports |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
272 referrals. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
273 - for load balancing this works just fine, but what about shared |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
274 mailboxes which require different UID? If we login with our own |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
275 username, we end up with our own UID instead of what we wanted. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
276 IMAP URLs don't support separated authorization id which would |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
277 have made this very easy.. We could give the "userid@group" as |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
278 userid, but clients probably treat it as different userid and |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
279 ask the password again. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
280 - problems, problems, .. maybe not worth the trouble. |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
281 - drafts: |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
282 - http://www.imc.org/ids.html |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
283 - annotate (draft-ietf-imapext-annotate) |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
284 - per-message annotations. this will be major change. especially |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
285 because currently there's no suitable storage for them, and |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
286 they'll probably change all the time.. maybe if we moved into |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
287 berkeley db to store the .data file and these annotations. |
| 1178 | 288 - this is separate problem from index files. indexes are treated as |
| 289 temporary files, annotations are permanent data. we'd have to | |
| 290 support non-db way to do this too, which would probably be just a | |
| 291 simple (slow) text file. | |
| 5621 | 292 - use lib-dict probably |
| 293 - metadata (draft-daboo-imap-annotatemore) | |
|
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
294 - server and per-mailbox annotations. much easier than |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
295 per-message annotations, but they'd be easier to place into |
|
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
296 db as well. |
| 5621 | 297 - lib-dict, again |
|
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
298 - binary (draft-nerenberg-imap-binary) |