- dovecot - dovecot.org

[Dovecot] maildir and the separator for subfolder
by David Bonnafous 15 Feb '07

15 Feb '07

hi, I use dovecot 1.0rc15 with one maildir namespace. I'd like to be able to use '.' in folders and subfolders name. So, I setup the default namespace with separator =':' But, when I create some folders and then subfolders with thunderbird the filename one the server are named with some '.' no ':'... It seems that dovecot always interprets '.' as a separator for folders. Is-it a bug ? yours, -- David Bonnafous Institut de Mathématiques Université Paul Sabatier Toulouse - France

4 5

[Dovecot] [Fwd: Compiler warnings]
by Stephen Lee 15 Feb '07

15 Feb '07

Hi, I'm resubmitting the message below hoping it gets a response this time. Thanks, Stephen -------- Forwarded Message -------- > From: Stephen Lee <splee(a)plexio.com> > To: dovecot(a)dovecot.org > Subject: [Dovecot] Compiler warnings > Date: Thu, 08 Feb 2007 08:27:48 -0800 > > Hi, > > I'm trying to install Dovecot 1.0RC22 on an old Trustix 1.5 box and am > getting the compiler warnings: > > quota-storage.c:275: warning: pointer of type `void *' used in > arithmetic > > convert-storage.c:50: warning: pointer of type `void *' used in > arithmetic > > acl-backend-vfile.c:212: warning: pointer of type `void *' used in > arithmetic > > There are many more of these pointer warnings in the various modules > when compiling. Is this a problem? > > Thanks, > Stephen >

3 3

[Dovecot] deliver LDA permission problem
by Dick Middleton 15 Feb '07

15 Feb '07

Hello, I'm trying to get deliver LDA working with postfix in a virtual domain configuration. I'm using dovecot v1.0.rc10. My setup is pretty much exactly as in the wiki (only the path to deliver and auth-master socket are different). I'm having a little problem with permissions and this occurred which I think is undesirable: syslog: Feb 8 13:09:35 deliver(<email-addr>): setgid(5002) failed: Operation not permitted Feb 8 13:09:36 deliver(<email-addr>): setgid(5001) failed: Operation not permitted mail.log: Feb 8 13:09:36 Devil postfix/pipe[9622]: 5AD5C103C: to=<<email-addr>>, orig_to=<<email-addr>>, relay=dovecot, delay=0.05, delays=0.01/0/0/0.04, dsn=5.3.0, status=bounced (Command died with status 89: \"/usr/libexec/dovecot/deliver\") When deliver fails because it can't connect to auth-master socket it returns an undeliverable status which causes postfix to defer delivery. I think it should do the same here. The real question is how I give deliver the permission to do the setgid? Is it enough to just add user vmail to each of the virtual user groups in /etc/group. Does deliver setuid to virtual user as well? Dick

3 4

[Dovecot] dict quota not being updated for all users when receiving a multi-recipient message
by Justin McAleer 15 Feb '07

15 Feb '07

I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1. I don't even have a guess as to what might be going on here, since each instance of the lda is a separate process. But, let me know if anybody has any ideas or requests for more info.

2 2

[Dovecot] sieve plugin
by pod 15 Feb '07

15 Feb '07

I'm currently looking at dovecot for a large-scale deployment. The requirements will almost certainly mean we would use the dovecot lda with the sieve plugin. The current method of distribution causes (binary distro) packaging to be slightly awkward IMHO. The dovecot-sieve code needs to be told where an in-tree build of dovecot lives. The fact that it _must_ be an in-tree build I was considering as a bug; the dovecot-sieve build wants to access both '.a' and '.h' files from the dovecot build but in an out-of-tree build these are in different places. My first thoughts were to simply move the dovecot-sieve code into the dovecot tree (I imagine under src/plugins/cmusieve or similar) and rework the autoconf setup as appropriate. This sidesteps the problem for this case but does not help other 'third party' dovecot plugins. If however a simple plugin build environment were to exist as part of a dovecot install then plugins could be distributed and built as independent packages. I quite understand that this additionally burdens dovecot development with 'stable API' concerns which may not be considered worth the effort. Timo: have you thought about any of the above and if so which direction have your thoughts taken you? I can justify spending a small amount of time to develop this into real code but it would be a waste to fight against or duplicate existing effort that has gone into this area. All comments welcome.

2 1

[Dovecot] leaking file descriptors? imap-login: inotify_init() failed
by Dale Bewley 15 Feb '07

15 Feb '07

Even though the system is configured to allow a large number of open files, and tools such as lsof tell me dovecot is within that limit; I am seeing errors like this pretty frequently. dovecot: imap-login: inotify_init() failed: Too many open files I'm running Fedora Core 5 (2.6.18-1.2257.fc5 SMP x86_64) with dovecot-1.0-1.rc15 built from the FC6 SRPM, but I was seeing the same thing with 1.0-0.beta8.3.fc5 (one of the reasons for the jump to the FC6 ver). # system default limit is very high, and we aren't approaching it [root@mail 2496]# cat /proc/sys/fs/file-max 738223 [root@mail fs]# cat file-nr 8704 0 738223 # the limit per user is 1024 [root@mail 2496]# su -c 'ulimit -n' dlbewley 1024 # But dovecot doesn't appear to be above that. # it looks like the master process is well below that [root@mail 2496]# lsof -p `cat /var/run/dovecot/master.pid` | wc -l 280 # but overall, this user has way more than that [root@mail fs]# lsof -nu dovecot |wc -l 3145 So, I raised the limit for dovecot to 5000 soft and 10000 hard to see if it would make a difference. Even after a reboot, the next day the errors returned. Today login_process_per_connection is set to 'no' rather than the default to see if it makes a difference. So far today, no errors. Config looks like this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/mail.cert ssl_key_file = /usr/share/ssl/private/mail.key disable_plaintext_auth = no login_process_per_connection = no max_mail_processes = 2048 protocol imap { } protocol pop3 { } auth_username_chars = auth_master_user_separator = * auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/dovecot.masterusers master = yes pass = no } passdb pam { } userdb passwd { } user = root } plugin { } -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3

2 1

[Dovecot] POP3-Proxy error
by Christian Froemmel 15 Feb '07

15 Feb '07

Hi, as mentioned in another thread I discovered a crash in the pop3-proxy. It occurs when the remote-pop3-server just drops the connection (in my case courier was hitting the MAXPERIP-Limit). I don't have a corefile yet, but will try to get one. Here the message from the dovecot.log: dovecot: Feb 02 09:30:00 Error: pop3-login: file pop3-proxy.c: line 20 (proxy_input): assertion failed: (!client->destroyed) dovecot: Feb 02 09:30:00 Error: pop3-login: Raw backtrace: pop3-login [0x8052fe0] -> pop3-login [0x8052ab4] -> pop3-login(vfprintf+0x2324) [0x804c6fc] -> pop3-login(vfprintf+0x2c9a) [0x804d072] -> pop3-login(vfprintf+0x1086) [0x804b45e] -> pop3-login(vfprintf+0x29d0) [0x804cda8] -> pop3-login [0x8056346] -> pop3-login [0x8055849] -> pop3-login(vfprintf+0x39d6) [0x804ddae] -> /lib/i686/libc.so.6(__libc_start_main+0xc7) [0x4015bd17] -> pop3-login(SSL_write+0x49) [0x804a931] dovecot: Feb 02 09:30:00 Error: child 5985 (login) killed with signal 6 It seems that the unexpected shutdown of the connection confuses dovecot. When I increased the MAXPERIP-limit in courier the crashes went away. regards, Christian -- SYSTEM CONCEPT GmbH

2 1

[Dovecot] master user
by Tom Bombadil 15 Feb '07

15 Feb '07

Greetings all... We are thinking about using the master DB, so a few admins can impersonate an ordinary user. So, we want to define one master for a set of users. And this administrator cannot be master of the other users? Can this be done somehow? Reading the docs, it seems that if a user is defined as master, it can login as everyone. Thanks for any hint.

4 3

[Dovecot] Startup errors
by Steven F Siirila 15 Feb '07

15 Feb '07

I just finished setting up a test Dovecot server (1.0-rc15, Solaris 10) and noticed upon start of Dovecot (after rebooting the server) that the imap-login and pop3-login processes spew errors as follows, which I can only assume is due to the fact that dovecot-auth has not fully initialized yet... it seems to me that these login processes are getting started too early, or should at least be waiting for dovecot-auth to get started. Jan 31 15:55:06 hostname dovecot: Dovecot v1.0.rc15 starting up Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 1 time Jan 31 15:55:07 hostname dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times Jan 31 15:55:07 hostname dovecot: pop3-login: Can't connect to auth server at default: Connection refused Jan 31 15:55:07 hostname last message repeated 9 times -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] Q on configuring shared mboxes
by Mikhail Teterin 15 Feb '07

15 Feb '07

Hello! I have the following three types of mailboxes on my server: 1) Regular user mail /var/mail/<user> in mbox format 2) Suspected spam in /var/tmp/spamprobe in mbox format 3) Archived mailing list in /home/mks/mksarch in mbox format I want the 1) to be only accessible to the respective <user>, obviously (POP3 and/or IMAP4). I wanted the 2) to be accessible to all users -- and I want them to be able to move stuff out of it into their own mboxes (IMAP4 is enough). I want the 3) to be accessible _read only_ to anyone, who enters the correct username/password (preferably -- without creating a special Unix account). (IMAP4 or POP3) So far, I have only been able to achieve 1). Could someone, please, help me configure dovecot for the 2) and the 3)? Thanks! -mi

2 1