Mercurial > dovecot > original-hg > dovecot-1.2
annotate TODO @ 497:4ff240ec007a HEAD
updated
author | Timo Sirainen <tss@iki.fi> |
---|---|
date | Thu, 24 Oct 2002 04:55:19 +0300 |
parents | 40b7d6ca51e3 |
children | ab394352fcb3 |
rev | line source |
---|---|
474 | 1 - if we deleted mail but didn't write modify log, other dovecots don't |
2 handle it properly. they either assert at index-sync.c:42 or if new | |
3 mails have also been added since, they don't notice it at all | |
480 | 4 actually, that breaks reads as well since we get expunges only from |
5 the old file.. and check that deleting file does "inconsistency error" | |
6 - if we have entries in modifylog with UID 10..11, 9..12, 8..13 etc. | |
7 do they work correctly? | |
8 - if imap process notices that both modify logs are getting full because it's | |
9 client isn't syncing, the client should be disconnected | |
474 | 10 |
480 | 11 - maildir: if mail file isn't found, it may be because it was renamed |
12 (flag changed). we must then sync the directory and see again if the mail | |
13 is found | |
14 - allow index files to be in completely separate location than mail data. | |
15 mails could be read through slow NFS access but indexes from fast local | |
16 disk. with this thinking it makes more sense to create larger index files | |
17 to save for example mail headers. also index rebuilding should be very | |
18 light operation, the indexes would be filled while the data is being | |
19 accessed by the imap client. of course all this should be optional so | |
20 we don't slow down when mails and indexes are stored in same disk. | |
21 - mail-lockdir.c isn't 100% safe.. stale locks are detected by checking that | |
22 hard link count is 1, then it's unlink()ed. but what if another process | |
23 did the same unlink() + creat() in the middle of our stat()..unlink()? | |
24 - MAP_SHARED with NFS doesn't update well. add option to update sync_id | |
25 after every change in file. when reading, if sync_id hasn't changed also | |
26 check with lseek()+read() if it has changed. | |
497 | 27 - mail-index.c needs to keep track if file has been modified, which is |
28 a bit difficult since it's done in so many places | |
29 - do we want it after all? indexes aren't required and they'd be slow | |
30 through NFS. | |
474 | 31 - RENAME: If the name has inferior hierarchical names, then the inferior |
32 hierarchical names MUST also be renamed (ie. foo -> bar renames | |
33 also foo/bar -> bar/bar). (and RENAME INBOX!) | |
34 - passwd-file doesn't notice changes in the file | |
35 - tree has some locking issues while opening it | |
36 - SEARCH FROM/TO/CC/BCC now generates the field from ENVELOPE which it uses | |
37 for matching. This however gives different results than when matching from | |
38 headers. | |
497 | 39 - when fetching body/envelope we could try to cache it immediately if |
474 | 40 we can get lock with try_lock. |
497 | 41 - we need permanent storage for UIDs. with mbox use X-UID like UW-IMAP, |
42 with maildir a) file:2,flags,Uuid b) file,U=uid:2,flags. uid validity | |
43 would be in .uidvalidity file. the b-case would require that to be done | |
44 by the client moving it from new/ to cur/ | |
45 - other possible maildir flags to use in filename: S=size (file size, | |
46 for maildir++ quota), W=size (rfc822.size by some uw-imap patch) | |
474 | 47 - mbox: what if 1 msg is deleted is x-imapbase rewritten? |
48 - check that search message-id worked properly always | |
49 - check that search's OR and () work properly | |
50 | |
51 - are the lowwater marks always reset to 0 when they don't exist? could be | |
52 just as well set to next_uid.. | |
53 - optionally use only in-memory indexes | |
54 - mbox handling is too slow, uw-imapd is much faster | |
55 - maildir could support also the dirty-flag in messages. files would be | |
56 renamed "whenever there's time" (that'd require the indexer program, or | |
57 forking and doing it in background) | |
58 - optionally keep the message file name as it's UID. Then we don't have to | |
59 save the filename anywhere. | |
60 - Should SEARCH SENT* apply timezone? | |
61 | |
0 | 62 test: |
63 - make sure locking is done properly when opening/switching modifylog | |
64 - make sure SELECT rebuilds index properly when next_uid is near 32bit value | |
65 - make sure connection limits work | |
474 | 66 - make sure modify log works properly, especially |
67 - switching the files | |
68 - seq1:seq2 ranges made a lot of changes | |
0 | 69 |
70 index: | |
71 - mbox: | |
96 | 72 - if a file isn't valid mbox and it's tried to be opened, say it in one |
73 line in error log, not 6.. | |
299 | 74 - locking: if we set shared lock to it while we're accessing it, we could |
75 get it pretty reliable. this means that the mbox fd needs to be locked | |
76 before sync() and kept locked after that until we're done with it. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
77 - requires mbox file to be open all the time. i guess that's fine. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
78 - expunge requires dropping the shared lock and getting exclusive |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
79 lock. after that we must sync again to make sure the file wasn't |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
80 changed. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
81 - could be done in index->set_lock() and try_lock(). in that case |
474 | 82 ignore the above. sometimes (quite often?) this is a bit useless |
83 since we're not touching the mbox file, but overall it simplifies | |
84 things a log | |
85 - mbox_file_open() could re-open() the file only when sync() has | |
86 noticed that the file inode/etc. have changed. it could also | |
87 cache the ibuffer as long as the mbox file is being locked | |
88 (ie. can't cache between locks, since the file may be shrinked) | |
304 | 89 - empty lines at beginning of file still aren't ignored |
474 | 90 - UW-IMAPd writes empty spaces after X-Keywords which it uses so that |
91 it doesn't have to rewrite the whole file if status flags changed | |
92 in the beginning of it. We could do that too. | |
93 - we need either From-line escaping or writing Content-Length | |
61 | 94 - read-only support for mailboxes where we don't have write-access? Maybe, |
95 but don't try to use their indexes since that's way too problematic, and | |
96 probably even impossible since we can't lock it. | |
235 | 97 - we should try to avoid completely rebuilding indexes unless they're |
98 corrupted. especially if we later want to support some read-only boxes | |
99 and keep the mail flags only in index file. fsck() could verify that | |
100 records are ok, and that if data file isn't ok the record is deleted. | |
101 - if .customflags is removed and Maildir files have custom flags, add | |
102 "unknown1" "unknown2" etc. flags to .customflags file for each found flag | |
103 - debug: index could be read-only mmaped when it's not locked. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
104 - when index is being rebuilt, it always complains about tree/modifylog |
313 | 105 having wrong indexid.. |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
106 - we sometimes leave some space in the index files (memory alignment, |
337 | 107 extra_space). we should keep those bytes zeroed to make sure nothing |
108 sensitive is left there. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
109 - tree file is never shrinked |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
110 - tree has some locking issues while opening it |
474 | 111 - log transferred amount of bytes. just a bit problematic who logs it, since |
112 imap-login does SSL transfers but not unencrypted.. could also log SSL | |
113 settings (especially compression). | |
114 - if we wanted to support huge mailboxes with small memory usage, it'd now | |
115 be possible if we just instead of mmap()ing the whole index files would | |
116 have maybe 3-4 256k mmap()ed areas which we move based on the need. | |
117 - should work fine with .imap.index and .imap.index.data | |
118 - log files aren't affected by mailbox size | |
119 - if the tree file also kept constantly moving the nodes so that | |
120 tree's root was at the beginning of the file, we could use this mmap | |
121 caching with it too | |
122 - but, is it worth the trouble really? the OS can do all this itself, | |
123 only thing we're doing is keeping the processes virtual memory usage | |
124 small. | |
0 | 125 |
126 lib-storage: | |
127 - support multiple mailbox formats and locations for one user. that would | |
128 require support for multiple MailStorages, and since we're chroot()ed, | |
129 usually the only way to communicate with others would be to create | |
130 RemoteMailStorage which would use TCP/UNIX sockets to connect to another | |
131 imap session. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
132 - SEARCH: |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
133 - CHARSET support, iconv()? also means we need to parse the charset stuff |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
134 in headers. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
135 - could optionally support scanning inside file attachments and use |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
136 plugins to extract text out of them (word, excel, pdf, etc. etc.) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
137 - use a trie index for fast text searching, like cyrus squat? |
0 | 138 - DELETE/RENAME: when someone else had the mailbox open, we should |
139 disconnect it (when stat() fails with ENOENT while syncing) | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
140 - RENAME INBOX isn't atomic with Maildir. And in general, RENAME can't |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
141 move mails between different storages. Maybe support doing also using |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
142 COPY + delete once COPY is atomic? |
337 | 143 - maildir: atomic COPY could be done by having transaction directories. |
144 Make a "tra" directory at the same level as cur/new/tmp, and make it | |
145 have subdirectories in the same way as tmp has temp files. Directory | |
146 begins with a "." as long as transaction isn't finished, rename()ing | |
147 it away finishes it. All mails under finished dirs must be moved into | |
148 new/ directory and the directory removed by any process who notices them. | |
61 | 149 - we should probably do some light checking that appended mails actually |
150 look like valid rfc822 mails.. | |
235 | 151 - maybe limit the length of custom flags? we don't really have a problem |
152 with them, but with mbox a long X-IMAPbase could break something.. Maybe | |
153 configurable, default to 50 chars? | |
337 | 154 - we could send flag changes after all commands by making expunge/flags sync |
155 counters separate for modify log. flags would need to update the seq | |
156 though, too slow? | |
157 - things calling message_send() could verify that it wrote enough data. | |
480 | 158 if not, fill the rest with spaces and return failure. -1 = error, |
159 0 = filled, 1 = ok. | |
0 | 160 |
161 general: | |
474 | 162 - sieve (rfc3028) |
337 | 163 - rfc2231 continuation support |
0 | 164 |
235 | 165 - ulimit / setrlimit() should be set somewhere for imap process |
0 | 166 - create indexer binary |
235 | 167 - SIGHUPing master should reload the configuration .. killing imap-auth and |
168 imap-login processes? or just signal imap-login to stop accepting new | |
169 connections and let it kill itself | |
299 | 170 - setting for choosing mbox locking methods |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
171 - imap-login leaks I/O descriptors when killed, that's because the SSL |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
172 fds are destroyed lazily.. should we bother fixing..? |
235 | 173 - logins are always sent now using syslog(), we'd need to have i_info() |
174 or something so they could also be written to log files.. also make it | |
175 possible to log into different log than errors. | |
176 - should we bother checking if there's invalid 8bit headers in | |
340 | 177 BODY/BODYSTRUCTURE output and converting them to quoted printable? well, |
178 several of them are now but not all.. | |
235 | 179 - update docs/index.txt |
337 | 180 - support Maildir++ quota |
181 - maybe give more untagged NO/ALERT replies? like when mailbox is in | |
474 | 182 inconsistent state. and when UIDs are reordered because they're too large. |
497 | 183 - *_strdup_printf() functions could use C99 compatible vsnprintf() instead of |
184 printf_string_upper_bound(). | |
185 - imap/ and lib-imap/ should allow infinite number of custom flags, it's | |
186 storage's problem if it can't handle too many of them. | |
61 | 187 |
188 auth / login: | |
337 | 189 - kchuid, SRP, anonymous SASL |
61 | 190 - PAM: support some options so /etc/passwd-lookup isn't needed. uid=x, gid=y, |
191 mailroot=/var/mail. maildirs should be then created when needed | |
0 | 192 - Digest-MD5: support integrity protection, and maybe crypting. Do it |
193 through imap-login like SSL is done? | |
194 - imap-auth should limit how fast authentication requests are allowed from | |
195 login processes. especially if there's one login/connection the speed | |
235 | 196 should be something like once/sec. also limit how fast to accept new |
197 connections. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
198 - Diffie Hellman parameters should be regenerated once in a while |
61 | 199 - HIGH: support executing each login in it's own process, so if an exploit |
200 is ever found from it, the attacker can't see other users' passwords. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
201 - master should limit number of login processes to max_logging_users, |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
202 killing old processes when limit is reached |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
203 - master should try to keep login_processes_count extra processes all |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
204 the time |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
205 - login should notify master after it accept()s, and it must close the |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
206 listening socket immediately |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
207 - Diffie Hellman parameters for SSL need to be somehow transferred |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
208 between login processes. It's too slow if they're generated every time, |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
209 and I'd rather not link SSL libs to imap-master. |
18 | 210 |
211 cleanups / checks: | |
212 - grep for FIXME | |
213 - check if t_push()/t_pop() should be added somewhere | |
214 - allocating readwrite pools now just uses system_pool .. so pool_unref() | |
215 can't free memory used by it .. what to do about it? at least count the | |
235 | 216 malloc/free calls and complain if at the exit they don't match |
61 | 217 - ..wonder what it would look like if I did s/FooBarBaz/struct foo_bar_baz/.. |
218 - HIGH: Make sure messages of size INT_MAX..UINT_MAX (and more) work | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
219 correctly with 32bit file offsets. virtual_size can also overflow making |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
220 it less than physical_size. |
96 | 221 - create env_put() and env_clean() |
235 | 222 - nearest_power() could be problematic with things that want it for ints, |
223 not size_t.. | |
474 | 224 - when sending lots of data with io_buffer_send(), it does a lot of |
225 io_add() and io_remove()s. and io_remove() just marks it destroyed, so | |
226 it may creates lots of IOs before the next ioloop run.. Though now it | |
227 doesn't matter much since we're corked and we don't create the IOs, | |
228 but ioloop should probably be fixed anyway. | |
0 | 229 |
230 optional optimizations: | |
231 - provide some helper binary to save new mail into mailboxes with CR+LF | |
232 line breaks? | |
233 - disk I/O is the biggest problem, so split the mail into multiple computers | |
234 based on user and have a proxy in the front redirecting the connection. | |
235 cyrus had something like this except a lot more complicated - it tried | |
236 to fix the problem of having shared mailboxes. we have the same problem | |
293 | 237 with local shared mailboxes as we don't use same UID for everyone's mail |
238 and we may be chrooted, so locally we could communicate with UNIX sockets, | |
239 remotely that could be done with TCP sockets. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
240 |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
241 capabilities: |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
242 - 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
|
243 option (--without-capabilities=acl,namespace,...) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
244 - possibility to disable them from config file |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
245 - 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
|
246 - 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
|
247 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
|
248 configurable however. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
249 - shared namespaces? maybe configurable in config file |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
250 - 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
|
251 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
|
252 maybe we could support it. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
253 - 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
|
254 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
|
255 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
|
256 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
|
257 anyway. ACLs could be stored into ".acl" ascii file in each folder. |
480 | 258 - support for private and shared flags, configurable by mailbox admin. |
259 this isn't in any draft yet, but ACL2 author was going to create one. | |
260 [SHAREDFLAGS (...)] would specify which ones are shared, don't know yet | |
261 how they would be configured. | |
376
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
262 - quota (rfc2087, draft-cridland-imap-quota) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
263 - give filesystem values only to admins |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
264 - 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
|
265 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
|
266 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
|
267 - id (rfc2971) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
268 - 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
|
269 - separate pre/post-login settings |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
270 - 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
|
271 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
|
272 "Disconnected", etc. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
273 - 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
|
274 especially before logging |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
275 - mailbox-referrals (rfc2193) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
276 - 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
|
277 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
|
278 requiring another UID to run. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
279 - 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
|
280 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
|
281 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
|
282 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
|
283 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
|
284 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
|
285 referrals. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
286 - 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
|
287 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
|
288 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
|
289 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
|
290 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
|
291 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
|
292 ask the password again. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
293 - problems, problems, .. maybe not worth the trouble. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
294 - literal+ (rfc2088) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
295 - simple. in case of invalid data, just disconnect client. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
296 - idle (rfc2177) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
297 - just call the syncing every few seconds (configurable) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
298 - with Linux we can use fcntl() and F_SETSIG to provide fast checks. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
299 just make sure sync() still won't be called more than once in a |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
300 few seconds |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
301 - uidplus (rfc2359) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
302 - uid expunge: no problem |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
303 - append, copy: oh no. these would slow down things and make |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
304 handling them much more difficult. currently we just store the |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
305 mails to destination mailbox without touching the indexes. since |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
306 we'd need to know their final UID, we'd have to lock the indexes |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
307 and mbox) fsck() first and append() next to find out the uid, |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
308 maildir) move the mail directly into cur/ and index it. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
309 - unselect (no draft or anything AFAIK) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
310 - like CLOSE, but doesn't expunge mails. easy. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
311 - drafts: |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
312 - http://www.imc.org/ids.html |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
313 - multiappend (draft-crispin-imap-multiappend) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
314 - shouldn't have any problems |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
315 - listext (draft-ietf-imapext-list-extensions) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
316 - well, it expired January 2002.. I like it though. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
317 - children (draft-gahrns-imap-child-mailbox) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
318 - I like listext more.. They have the same functionality though, |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
319 so pretty easy to support both if needed |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
320 - annotate (draft-ietf-imapext-annotate) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
321 - 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
|
322 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
|
323 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
|
324 berkeley db to store the .data file and these annotations. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
325 - annotatemore (draft-daboo-imap-annotatemore) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
326 - 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
|
327 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
|
328 db as well. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
329 - binary (draft-nerenberg-imap-binary) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
330 - 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
|
331 binary-safe though. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
332 - sort (draft-ietf-imapext-sort) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
333 - basically sorted SEARCH, requiring CHARSET support for |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
334 UTF-8 and ASCII |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
335 - we could create alternative binary tree file(s) for different sort |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
336 conditions, ".tree-sort" or something. or if we decide to just |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
337 keep it in memory, btree could still be best choice. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
338 - required by squirrelmail (webmail) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
339 - thread (draft-ietf-imapext-thread) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
340 - basically SORT but reply with thread lists |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
341 - possibly use a binary tree too .. or maybe it's enough to use the |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
342 sort-tree and then just pick up the references separately? have to |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
343 check more carefully later. |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
344 - view (draft-ietf-imapext-view) |
fd1fc4cf11b7
updated with lots of new capability comments
Timo Sirainen <tss@iki.fi>
parents:
340
diff
changeset
|
345 - 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
|
346 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
|
347 - can be done client-side just fine (evolution's virtual folders) |