Re: [Dovecot] Plugin delete-to-trash on Dovecot 2.0
I contacted Lex Brugman about the delete-to-trash plugin for dovecot 2.0, he told me there's no version compatible with 2.0 yet... So I looked at the code and started to adapt the code for dovecot 2.0. I have 0 experience with dovecot plugin development, but with a quick adaptation, I managed a apparently stable plugin version, based on deleted-to-trash 0.3. I'm using since last friday with Dovecot 2.0.9 with ~30 imap users. Tested deletion and restore with individual messages, 1000, and 2000 messages. Emerson Pinter On 22-12-2010 14:26, Antonio Perez-Aranda wrote: There are some body using delete-to-trash on any version of Dovecot 2.0? deleted-to-trash-plugin_0.3_test_for_dovecot_20.tar Description: Unix tar archive
Re: [Dovecot] Plugin delete-to-trash on Dovecot 2.0
Thank you, Timo. I will test. Emerson Pinter Picture Internet +55-11-5089-8100 http://www.picturemail.com.br/ http://www.picturesecurity.com.br/ http://www.picture.com.br/ On 01-02-2011 18:25, Timo Sirainen wrote: I didn't really look at the logic itself, but attached patch fixes/cleans up a couple of things. On Tue, 2011-02-01 at 17:48 -0200, Emerson Pinter wrote: I contacted Lex Brugman about the delete-to-trash plugin for dovecot 2.0, he told me there's no version compatible with 2.0 yet... So I looked at the code and started to adapt the code for dovecot 2.0. I have 0 experience with dovecot plugin development, but with a quick adaptation, I managed a apparently stable plugin version, based on deleted-to-trash 0.3. I'm using since last friday with Dovecot 2.0.9 with ~30 imap users. Tested deletion and restore with individual messages, 1000, and 2000 messages. Emerson Pinter On 22-12-2010 14:26, Antonio Perez-Aranda wrote: There are some body using delete-to-trash on any version of Dovecot 2.0?
Re: [Dovecot] cgroup support
I think the current pid(from postlogin script) is sufficient if the imap binary will be a child process. The cgroup is inherited from parent process (at least the kernel documentation says that)... Emerson Pinter On 30-01-2011 14:10, Timo Sirainen wrote: On Sun, 2011-01-30 at 17:03 +0100, Andreas Pelme wrote: On 30 jan 2011, at 16:05, Emerson Pinter wrote: Have you tried post login scripts ? Wow, I had missed the post login scripts. That will solve this problem very nicely! Hmm. With v1.x it works, but in v2.0 the post-login scripts are run in a separate process and I don't think you can get the PID there without some changes to code..
Re: [Dovecot] cgroup support
Have you tried post login scripts ? On Sun, 30 Jan 2011 13:28:22 +0100, Andreas Pelme andr...@pelme.se wrote: Hi, I am setting up a system that enforces cgroup restrictions when a user logs in via SSH, and for all the services that are run by a particular user. I am also running dovecot to give users IMAP/POP access to their mailboxes. However, to be part of a cgroup, PIDs must be explicitly added to the cgroup tasks file. So for now, all my processes are run with resource restrictions, except for Dovecot processes. It would be really cool if dovecots child/worker processes could be added the a cgroup in addition to the usual setuid/chroot protections that already exists. Adding a process to a cgroup is a matter of writing the PID to the correct cgroup tasks file. If this were implemented as an extra field in userdb, it could be very powerful, and allow for all kinds of resource management/accounting of dovecot processes. This would obviously not be cross-platform, since cgroups are a feature of the Linux kernel. Would that be a problem? Is support for cgroups something that could be considered for dovecot at all? Are there other ways to put dovecot processes in cgroups? I do not really have a patch or a plan for how everything would work out in detail. If this would be useful for dovecot, I would be happy to start hacking on a patch. Cheers Andreas -- Emerson Pinter Picture Internet +55 11 5089 8100 http://www.picture.com.br/
Re: [Dovecot] Master User Features I'd like to see
You can use checkpassword:
http://wiki.dovecot.org/AuthDatabase/CheckPassword
Works fine for me for master user authentication.
Emerson Pinter
On 15-08-2010 18:46, Marc Perkel wrote:
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what
I want with the right kinds of variable passing that doesn't yet
exist. Let me see if I can explain clearly.
From the example in the wiki:
auth_master_user_separator = *
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
userdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
Login looks like this:
# telnet localhost 143
* OK Dovecot ready.
1 login loginuser*masteruser masterpass
1 OK Logged in.
I'm assuming that the masteruser and masterpass is passed to the
master passdb and when doing so the variable %u is the master user. I
assume that %n and %d also represent the name and domain part of the
master user.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the
master user is master for that particular login user. That way I can
give domain owners or owners of multiple domains the ability to manage
the email accounts within their scope of permission.
Re: [Dovecot] Checkpassword/prefetch/master_user and prob lems
Nobody ?
This can be a dovecot bug ?
--
Emerson Pinter
Picture Internet
55 11 5089-8130
http://www.picture.com.br/
On Mon, 19 Apr 2010 14:27:22 -0300, Emerson Pinter
epin...@picturecorp.com.br wrote:
Hi.
I'm trying to use checkpassword for simple auth and masteruser auth.
I have two programs, one called checkpassword-master (for masteruser
lookup) and another called checkpassword for normal passdb and userdb
lookup).
All works fine for non-masteruser authentication (in this case dovecot
makes a single call to checkpassword binary). But if a master-user
authenticates, dovecot execute checkpassword-master binary, and then
executes checkpassword binary. Checkpassword binary receive the
MASTER_USER
env and do all the checks correctly, when checkpassword finish, dovecot
logs this message auth(default): checkpassword: sighandler called for
unknown child and authentication fails...
I'm trying checkpassword-reply and fd4 too, on 1.2.11 and 2.0b4, no
success.
Below is my config:
auth default {
mechanisms = plain
passdb checkpassword {
args = /srv/dovecot/checkpassword
}
passdb checkpassword {
args = /srv/dovecot/checkpassword-master
master=yes
pass=yes
}
userdb prefetch {
}
}
Anybody can help me ?
Tks.
Esta mensagem pode conter informações confidenciais, privilegiadas ou privadas.
Caso não seja o destinatário, favor apagá-la e notificar o remetente.
Saiba que o uso impróprio das informações existentes é estritamente
proibido, sendo tratado conforme as normas da empresa e a legislação em vigor.
