Timo Sirainen schrieb: > On May 27, 2009, at 2:22 AM, reg9009 wrote: > >> In my opinion, dovecot should give capabilities, regardless if before >> or after login sequence. What would be the problem of it or why would >> it be intented to be removed. It would actually just break with a >> rather common client and change behaviour to all previous versions. > > The problem is that the capabilities depend on what plugins are > loaded. It's also possible to have different plugins loaded for > different users, so the capability reply might depend on the user > logging in. So in such setups there's no way to give the correct > capability before the username is known. Even without that problem the > way to get the list of capabilities from plugins is pretty horrible > code and if there's a way to get rid of it I'd like that. > > Hmm, that's indeed a problem. Well, for the plugins depending on different users I don't have an answer. But I think TB is using the capability command again after login. I'll check.
For gathering the capabilities of plugins, etc. Would it be a viable solution to demand the plugins to pass capabilities at the point where the plugin registers/loads itself? That way it may not be that ugly? I have to apologize, I'm not that deep coder, so some ideas might be simple spoken... :) Regards, Sebastian
