Mercurial > dovecot > original-hg > dovecot-1.2
annotate TODO @ 3450:5c92b51f2b38 HEAD
updated
author | Timo Sirainen <tss@iki.fi> |
---|---|
date | Thu, 30 Jun 2005 23:38:48 +0300 |
parents | 769e2e2bf1d5 |
children | 3cc9212b1c66 |
rev | line source |
---|---|
3450 | 1 - calls fsync()s etc. less often (when copying). optionally disable them. |
2 - stop using atol(), atoi(), strtoul() etc. in places where we actually | |
3 care about what they return, and rather create our own function which | |
4 checks if the input overflows the integer, and if so call i_fatal() | |
5 - for master/config rewrite: make sure the log changes will work | |
6 - when sorting maildir files, sort based on Mxxxx first so the files are | |
7 sorted always in ascending order. required for proper out-of-quota uidlist | |
8 handling | |
9 - Panic: file mail-index.c: line 844 (mail_index_sync_from_transactions): | |
10 assertion failed: (hdr.messages_count == (*map)->hdr.messages_count) | |
11 - after some locking timeouts: mbox-lock.c: line 518 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) | |
12 | |
13 - Corrupted transaction log file dovecot.index.log: record size wrong (type 0x4, 20 % 12 != 0) | |
14 -> mail-index.c: line 841 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)->hdr.messages_count) | |
15 | |
16 - subscribe #maildir -> LSUB "" * -> probably not listed? | |
17 * 1807 EXISTS | |
18 * 0 RECENT | |
19 * OK [UNSEEN 1] First unseen. | |
20 * OK [UIDVALIDITY 1106090975] UIDs valid | |
21 * OK [UIDNEXT 38157] Predicted next UID | |
22 x OK [READ-WRITE] Select completed. | |
23 x store 500:* +flags.silent \deleted | |
24 * 31 RECENT | |
25 x OK Store completed. | |
3048 | 26 |
3450 | 27 - dovecot-auth workers: create a separate dovecot-pam worker which shares |
28 pretty much all code with dovecot-auth worker but isn't linked against | |
29 any libraries. or..? this might be difficult to do, especially because the | |
30 workers currently can handle any kind of passdb/userb requests. perhaps | |
31 there should be a completely separate simple PAM authenticator binary. | |
32 - namespaces: add new "auto_disable" flag so if the mailbox can't be opened | |
33 (eg. file doesn't exist), just ignore the problem and disable the namespace | |
34 diff -u -r1.44 cmd-list.c | |
35 --- src/imap/cmd-list.c 5 Feb 2005 18:07:26 -0000 1.44 | |
36 +++ src/imap/cmd-list.c 15 Mar 2005 16:15:27 -0000 | |
37 @@ -213,7 +213,7 @@ | |
38 ctx->inbox && cur_ref == ctx->ref, | |
39 ns->sep); | |
40 if (*cur_ref != '\0' || *cur_prefix == '\0') | |
41 - match = IMAP_MATCH_CHILDREN; | |
42 + match = ns->hidden ? IMAP_MATCH_NO : IMAP_MATCH_CHILDREN; | |
43 else { | |
44 len = strlen(cur_prefix); | |
45 if (cur_prefix[len-1] == ns->sep) | |
46 | |
47 | |
48 - auth master refcounting when handling user/request? | |
49 - prepend_uid is useless nowadays? | |
50 | |
51 - mail_index_map() -> sync from transaction log -> refresh -> mail_index_map() | |
52 - buffer_create_data() behavior has changed from silent-truncating to | |
53 hard-crashing. See if it breaks anywhere (PAM!) | |
54 - PAM / checkpassword should use passdb-blocking | |
55 - if capability is sent in greeting, it's not waiting for AUTH=xx.. | |
56 - if ssl isn't compiled in, it doesn't complain anything if it's tried to | |
57 be used .. and configure summary even says it's enabled | |
58 - SSL_read in -lssl -> no | |
59 | |
60 - deleting lots of messages for rarely opened box seems to cause trouble: | |
61 IMAP(cras:17105): Cached message offset lost for seq 93 in mbox file /home/cras/mail/bugtraq | |
62 IMAP(cras:21802): mbox sync: UID inserted in the middle of mailbox /home/cras/mail/bugtraq (816584 > 816580) | |
63 IMAP(cras:21802): mbox sync: UID inserted in the middle of mailbox /home/cras/mail/bugtraq (816598 > 816580) | |
64 | |
65 - solaris sendfile is broken? | |
3048 | 66 |
67 mail-index-transaction.c: line 467 (mail_index_transaction_add_last): | |
68 assertion failed:(idx == size || data[idx].uid1 <= update.uid1) | |
69 | |
3087 | 70 - keywords: |
71 - add some limits to how many there can be | |
72 - don't return \* in PERMANENTFLAGS when we're full | |
73 - send FLAGS/PERMANENTFLAGS untagged replies when they change | |
74 - remove unused keywords? | |
2774 | 75 |
76 - caching | |
3450 | 77 - cache _all_ existing headers when headers are being parsed, not just the |
78 ones client is requesting at that time. | |
3048 | 79 - size.physical isn't cached |
2774 | 80 - force bits should be used only for nonregistered fields |
81 - change envelope parsing not to use get_headers() so imap.envelope can | |
82 actually be cached without all the headers.. | |
83 - compression should drop fields with last_used < | |
84 (latest_mail_index_date - month) | |
85 - when parsing mbox or saving message, parse the mail through index-mail | |
86 so things gets saved into cache immediately | |
3087 | 87 - we can mail_cache_add() same header multiple times.. |
88 - get_field() doesn't work if it's not already cached | |
3450 | 89 - we could try compressing same field values into a single |
90 location in cache file. | |
91 - Most messages are text/plain/7bit/us-ascii/no-other-content-type-params. | |
92 Instead of saving tons of nearly identical BODY/BODYSTRUCTURE fields | |
93 into cache, we could just set INDEX_MAIL_FLAG_TEXT_PLAIN_7BIT_ASCII bit | |
94 on and generate the bodystructure for such messages on the fly. | |
95 - support caching all message headers. this could be useful when | |
96 indexes are in local disk but actual mails are accessed through NFS. | |
2774 | 97 |
3087 | 98 - mbox |
99 - syncing existing indexes takes 4x longer than creating new one, why? | |
100 - how well does dirty sync + status work? it reads the last mail every | |
101 time? not very good.. | |
102 - mbox file offsets still aren't 64bit aligned for some reason.. | |
103 - when we're updating flags with lazy writing, we're still parsing the | |
104 mbox, just not writing to it! | |
105 - always add empty line. make the parser require it too? syncing should | |
106 make sure there always exists two LFs at end of file. raw-mbox-stream | |
107 should make sure the last message ends with LF even if it doesn't exist | |
108 in the file | |
2774 | 109 - COPY doesn't work to itself (lock assert crash) |
2143 | 110 - keep mbox lock for two extra seconds after sync |
111 - move /var/mail/user to ~/mbox if ~/mbox exists.. supposedly this | |
112 could be useful if /var/mail doesn't have quota, but ~/mail does. | |
113 now, what do we then do if we can move only some of the mails?.. | |
114 - if we can't create dotlock file for mbox, make sure it still can be | |
115 selected in read-only state | |
116 | |
3087 | 117 - maildir |
118 - if indexes exist but dovecot-uidlist doesn't, it's not tried to be | |
119 recreated | |
120 - hardlink copying doesn't update indexes | |
121 - rename foo foo.xyz -> infinite loop possible? | |
122 - we probably shouldn't do duplicate detection/fixing?.. or at least stat() | |
123 the old file before trying, because we might have just previously seen | |
124 the old file and then new file and then we try to fix it.. | |
125 - if .customflags is removed and Maildir files have custom flags, add | |
126 "unknown1" "unknown2" etc. flags to .customflags file for each found flag | |
3450 | 127 - with pop3 don't move messages from new/ to cur/ before RETR |
3087 | 128 |
2143 | 129 - index |
3087 | 130 - if uoff_t or time_t size changes, don't rebuild indexes because they |
131 don't use them. just rebuild cache file. | |
132 - flag merging code is too complex in index syncing. it should be moved | |
133 into mbox/maildir syncing where they're combined | |
134 - mail_index_lookup_ext() doesn't handle resizes between views. probably | |
135 needs size_t *size_r parameter added.. | |
2143 | 136 - optimize initial left_idx in mail_index_lookup_uid_range() |
137 - when referencing log files, open them immediately? | |
138 - if log file is lost, generate it from old and new index | |
139 - make sure when changing flags multiple times in transaction it goes ok. | |
140 especially replace + dirty flag | |
3087 | 141 - transaction log: when replacing log with a same sequence, we remove it |
142 from log's file list, but we don't do anything to existing log views. | |
143 this can crash later in mail_transaction_log_view_set() because 'first' | |
144 is from log list, while we're comparing it into view->tail which it never | |
145 is. also overwriting it leaks memory.. | |
146 - read-only support for mailboxes where we don't have write-access | |
147 - when mailbox is deleted/renamed and someone else had it open, we get | |
148 stat() error messages in log file. | |
149 - sort: we could create alternative indexes for different sort conditions. | |
150 sort code itself already supports this optimization. | |
2143 | 151 |
3087 | 152 - lib-storage |
153 - index_removal_timeout gets leaked in some conditions. how? | |
154 - subscribe: IMAP(anonymous): open(anonymous/mail/.temp...) failed: Permission denied | |
155 - subscriptions file should contain namespace prefixes. at least optionally. | |
156 there's the subscriptions = yes setting now for namespaces.. do it so that | |
157 if prefix = "" has subscriptions, it contains prefixes. otherwise not. | |
158 - support zlib compressed mbox/maildir? mbox maybe just read-only. | |
159 do it through istream-zlib wrapper | |
160 - should we allow following symlinks in mbox/maildirs? they are now. | |
161 - if we implement shared mailboxes with shared indexes, never do that or | |
162 others could symlink your personal mailboxes and see the indexes | |
163 created for it which may contain envelope etc. data | |
164 - this allows circular mailbox hierarchies which should be prevented by | |
165 eg. allowing max. 20 hierarchies. | |
860 | 166 - limit folder hierarchy levels? user can now create eg. a/a/a/a/... |
167 and then start renaming them from end to beginning, which probably will | |
168 at some point start causing syscall failures which will fill up logs. | |
3087 | 169 |
170 - login | |
171 - Digest-MD5: support integrity protection, and maybe crypting. Do it | |
172 through login process like SSL is done? | |
173 - x login foo bar | |
174 x NO Authentication failed. | |
175 x login cras pass | |
176 * BYE Disconnected for inactivity. | |
177 ^ but it's not disconnecting! (buggy dovecot-auth not replying) | |
178 - imap-login: Authenticate PLAIN failed: Authentication failed: | |
179 Authentication server isn't connected, try again later.. [127.0.0.1] | |
180 ^ NO Authentication failed. (should be Temporary login failure!) | |
181 - if auth process dies, login process should retry authentication if | |
182 possible. or if not, disconnect the client so it doesn't think the auth | |
183 failed. | |
184 - send client IP immediately after accept() to master process. make sure | |
185 master shows the IP if login dies unexpectedly. master should probably | |
186 also kill the login process if it doesn't kill itself soon enough.. or | |
187 maybe just log the IP immediately. | |
474 | 188 |
3087 | 189 - auth |
190 - APOP is broken? | |
191 - support specifying hex/base64 encoding in password scheme. for example | |
192 {plain-md5.base64} | |
193 - auth protocol: make sure values can't have tabs/lfs | |
194 - auth cache: cache userdb data too. | |
195 - remove system_user and allow returning multiple gids instead. | |
196 - SIGHUP restarts auth processes .. but does it wait until they've finished | |
197 with all requests? no. | |
198 - post-login-sql-command | |
199 - does dovecot-auth really break when it runs out of fds? | |
200 - dovecot-auth should limit how fast authentication requests are allowed from | |
201 login processes. especially if there's one login/connection the speed | |
202 should be something like once/sec. also limit how fast to accept new | |
203 connections. | |
204 - support read-only logins. user could with alternative password get only | |
205 read-access to mails so mails could be read relatively safely with | |
206 untrusted computers. Maybe always send [ALERT] about the previous | |
207 read-only login time with IP? | |
526 | 208 |
3087 | 209 - master |
210 - pipe() failed: Too many open files - fine, but don't log it 1000 times | |
211 a second | |
212 - configurable syslog prefix | |
213 - SIGHUP rather shouldn't restart listening sockets if they didn't change.. | |
3450 | 214 - if there are duplicate settings, complain about it |
3087 | 215 |
216 - quota | |
217 - support Maildir++ quota | |
218 - if dovecot-uidlist can't be written, assume the new mails have UIDs | |
219 beginning from uidlist.next_uid. Whenever mails are expunged, overwrite | |
220 the next_uid field with the current highest next_uid. Whenever we have | |
221 assumed UIDs and uidlist gets updated, throw the client out with | |
222 "inconsist mailbox". | |
223 - make sure all syscalls check for ENOSPACE (and ENOACCESS while at it) | |
224 | |
225 - ssl | |
226 - add setting: ssl_options = bitmask. by default we enable all openssl | |
227 workarounds, this could be used to disable some of them | |
228 - open("/var/run/dovecot//ssl-parameters.dat", O_RDONLY|O_LARGEFILE) =-1 ENOENT | |
229 ^ loops forever | |
230 - gnutls support isn't working | |
634 | 231 - OpenSSL: support generated DH parameters |
1250 | 232 - SSL: Support password protected key files. Support reading the password |
2143 | 233 from user at runtime (dovecot startssl or something). currently it just |
234 hangs. | |
965 | 235 |
3087 | 236 - search |
237 - message header search: we should ignore LWSP between two MIME blocks | |
1250 | 238 - message_body_search() could accept multiple search keywords so we |
239 wouldn't need to call it separately for each one (so we wouldn't need | |
240 to parse the message multiple times). | |
241 - message_body_search() could support NULL MessagePart and the searching | |
242 could be done while parsing the message. this would need changes to | |
243 message_parse() as well. | |
244 - could optionally support scanning inside file attachments and use | |
245 plugins to extract text out of them (word, excel, pdf, etc. etc.) | |
246 - use a trie index for fast text searching, like cyrus squat? | |
247 - Create our own extension: When searching with TEXT/BODY, return | |
248 the message text surrounding the keywords just like web search engines | |
249 do. like: SEARCH X-PRINT-MATCHES TEXT "hello" -> * SEARCH 1 "He said: | |
250 Hello world!" 2 "Hello, I'm ...". This would be especially useful with | |
251 the above attachment scanning. | |
0 | 252 |
3087 | 253 - lib |
254 - file cache: last block in file isn't cached. | |
255 - ioloop-kqueue.c patch | |
256 - dotlocking: stale_timeout should probably take into account how old the | |
257 file is.. so uses more time with more recent locks.. | |
258 | |
259 - lib-charset | |
260 - utf8_toupper() is a must. and a bit difficult if we want to do it right. | |
261 - add support for other things than iconv() as well? we could reuse | |
262 the code from cyrus or courier | |
263 - cache iconvs? they'd probably be faster if we just reset the | |
264 conversion instead of opening new one every time. and there will likely | |
265 be only one or two charsets which are used for nearly all conversions. | |
266 | |
267 - general | |
1250 | 268 - sieve (rfc3028), we can use Cyrus Sieve |
3087 | 269 - rfc2231 continuation support (useless?) |
1553 | 270 - rfc2557 support for BODYSTRUCTURE, as specified by RFC3501 |
271 - lmtp server - is it needed? dovecot-deliver binary at least would be | |
272 useful | |
1250 | 273 - create indexer binary |
3087 | 274 - ~/.dovecotrc to override system wide settings. namespace settings should |
275 override all the previous namespace settings instead of adding new. | |
276 - ESTALE handling for NFS safety | |
277 - option to disable SORT, SEARCH and other memory/cpu-intensive features. | |
278 defaults and per-user by dovecot-auth. | |
279 - dotlock overriding is racy, but it's pretty difficult to fix it. Also | |
280 overriding someone else's dotlock in shared folder isn't possible. These | |
281 could be fixed by having separate lock process running as root, which | |
282 would chown() the file for another uid and then unlink() it as that user. | |
283 One problem with that is that if malicious user sets setuid+execute bits | |
284 on for the file, he could run the file and get changed to the new uid. | |
285 That hopefully shouldn't matter much since the new uid should be user | |
286 with minimum possible privileges. Anyway, optional.. | |
287 - 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
|
288 |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
289 capabilities: |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
290 - preferrably all should be possible to #ifdef away by a configure |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
291 option (--without-capabilities=acl,namespace,...) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
292 - possibility to disable them from config file |
3087 | 293 - THREAD=ORDEREDSUBJECT - although pretty useless I'd think. |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
294 - acl (rfc2086, draft-ietf-imapext-acl), namespace (rfc2342) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
295 - probably do it like cyrus. "user.<username>" to access other |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
296 users, with "" defaulting to "user.<myself>". these should be |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
297 configurable however. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
298 - shared namespaces? maybe configurable in config file |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
299 - easiest way to do ACL would be to use unix modes, but is that |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
300 useful at all? Well, ACL2 has a bit better support for that, so |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
301 maybe we could support it. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
302 - otherwise gets a bit trickly, we could keep all mail in "imapmail" |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
303 group and 0600/0700 mode by default, but when mail is shared to others, |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
304 the group read/write access bits would be set. or alternatively we |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
305 could launch another imap process to handle it, which we should support |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
306 anyway. ACLs could be stored into ".acl" ascii file in each folder. |
480 | 307 - support for private and shared flags, configurable by mailbox admin. |
308 this isn't in any draft yet, but ACL2 author was going to create one. | |
309 [SHAREDFLAGS (...)] would specify which ones are shared, don't know yet | |
310 how they would be configured. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
311 - quota (rfc2087, draft-cridland-imap-quota) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
312 - give filesystem values only to admins |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
313 - support for Maildir++, probably no need to support more. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
314 quota capability supports complex quota configuration, but if |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
315 no mailer supports them we probably shouldn't bother either |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
316 - id (rfc2971) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
317 - 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
|
318 - separate pre/post-login settings |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
319 - 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
|
320 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
|
321 "Disconnected", etc. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
322 - 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
|
323 especially before logging |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
324 - mailbox-referrals (rfc2193) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
325 - 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
|
326 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
|
327 requiring another UID to run. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
328 - 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
|
329 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
|
330 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
|
331 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
|
332 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
|
333 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
|
334 referrals. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
335 - 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
|
336 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
|
337 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
|
338 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
|
339 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
|
340 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
|
341 ask the password again. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
342 - problems, problems, .. maybe not worth the trouble. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
343 - drafts: |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
344 - http://www.imc.org/ids.html |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
345 - annotate (draft-ietf-imapext-annotate) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
346 - 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
|
347 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
|
348 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
|
349 berkeley db to store the .data file and these annotations. |
1178 | 350 - this is separate problem from index files. indexes are treated as |
351 temporary files, annotations are permanent data. we'd have to | |
352 support non-db way to do this too, which would probably be just a | |
353 simple (slow) text file. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
354 - annotatemore (draft-daboo-imap-annotatemore) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
355 - 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
|
356 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
|
357 db as well. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
358 - binary (draft-nerenberg-imap-binary) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
359 - perhaps not too useful. I'd like to make Dovecot fully |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
360 binary-safe though. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
361 - view (draft-ietf-imapext-view) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
362 - slow, complex, luckily draft expired almost two years ago. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
363 i hope i don't have to implement this :) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
364 - can be done client-side just fine (evolution's virtual folders) |