- dovecot - dovecot.org

Re: [Dovecot] many instances om imap and imap-login
by Dominic Marks 26 Apr '05

26 Apr '05

On Tuesday 26 April 2005 15:19, you wrote: > Thanks for extensive answer. > > I will look into all your suggestions. Please keep the mailing list in the response, it allows other people to provide advice, follow the conversation, and you get, hopefully, complete solutions stored in the archives waiting for Google to index. > Answers to you questions: > > Are the mailboxes being accessed via Webmail?: > yes they can but arent at the moment (squirrelmail) Webmail can cause lots of extra connections to me made. > What Mail application are your users using?: > Thunderbird 1.0.2 Don't have much experience with this client, although it works when I've tried it. Others may be able to provide experience here. > Have you checked what state the connections are in?: > Do you mean of they are connected or not? when I run top I do see > instances called IMAP owned by each user so I asume they are connected mail# netstat -f inet -p tcp | grep imap tcp4 0 0 mailserver.imap client01.1386 ESTABLISHED tcp4 0 0 mailserver.imap client02.1344 ESTABLISHED tcp4 0 0 mailserver.imap client01.1108 ESTABLISHED tcp4 0 0 mailserver.imap client03.54607 ESTABLISHED mail# netstat -a -f inet -p tcp | grep "*.imap*" tcp4 0 0 *.imaps *.* LISTEN tcp4 0 0 *.imap *.* LISTEN FreeBSD 5.4 with a few Outlook and KMail clients. > /jon > > Dominic Marks said the following on 2005-04-26 16:11: > >On Tuesday 26 April 2005 14:58, Jon wrote: > >>Hi, > >> > >>Im using dovecote as my IMAP interface. However i do have a lot of imap > >>instances. its only 7 user using the system as i get this. please advice. > > > >Having lots of processes running isn't automatically a bad thing, but you > > do > > > >seem to have quite a lot of imap and imap-login processes, so: > >>From a dovecot.conf on a server I run being used by about 7 people: > > > > (Comments are from dovecot-sample.conf) > > > ># Should each login be processed in it's own process (yes), or should one > ># login process be allowed to process multiple connections (no)? Yes is > > more # secure, espcially with SSL/TLS enabled. No is faster since there's > > no need # to create processes all the time. > >login_process_per_connection = no > > > >So if security is less of a concern than having many processes running, > > you should set this to no. > > > ># Number of login processes to create. If login_process_per_user is > ># yes, this is the number of extra processes waiting for users to log in. > >login_processes_count = 1 > > > >I set this low because I don't need the extra processes. > > > ># Maximum number of extra login processes to create. The extra process > > count # usually stays at login_processes_count, but when multiple users > > start # logging in at the same time more extra processes are created. To > > prevent # fork-bombing we check only once in a second if new processes > > should be # created - if all of them are used at the time, we double > > their amount until # limit set by this setting is reached. This setting > > is used only if # login_process_per_use is yes. > >#login_max_processes_count = 128 > > > >You might want to set this to something like 4? > > > ># Maximum number of connections allowed in login state. When this limit is > ># reached, the oldest connections are dropped. If login_process_per_user > ># is no, this is a per-process value, so the absolute maximum number of > > users # logging in actually login_processes_count * max_logging_users. > >#login_max_logging_users = 256 > > > >Probably no need to worry about this. > > > >>1230 ? S 0:00 imap-login > >> 1309 ? S 0:00 imap-login > > > > <snip> > > > >> 2387 ? S 0:00 imap-login 3095 ? S 0:00 imap > >> 3096 ? S 0:00 imap-login > >> > >>/jon > > > >Other things to think about: > > > >Are the mailboxes being accessed via Webmail? > >What Mail application are your users using? > >Have you checked what state the connections are in? > > > >HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK.

1 0

[Dovecot] can't chroot "auth process" (dovecot-1.0-test68)
by John Wong 26 Apr '05

26 Apr '05

OS: OpenBSD/i386 dovecot: dovecot-1.0-test68 dovecot can not start, when i chroot "auth process" can i defined the "auth-work.XXX" unix socket path?? mail.log ----------------------------------------- Dovecot v1.0-test68 starting up auth(default): mysql: Connected to (null) (mail) Auth process died too early - shutting down auth(default): net_connect_unix(/var/dovecot//auth-work.12922) failed: No such file or directory child 12922 (auth) returned error 89 ----------------------------------------- dovecot.conf ----------------------------------------- base_dir = /var/dovecot/ protocols = imap imaps pop3 pop3s ssl_cert_file = /etc/ssl/certs/mail.crt ssl_key_file = /etc/ssl/private/mail.key ssl_parameters_file = /var/dovecot/ssl-parameters.dat disable_plaintext_auth = no login_dir = /var/dovecot/login login_user = _dovecot login_processes_count = 1 valid_chroot_dirs = /var/spool/postfix/var/mail mail_debug = yes default_mail_env = maildir:%h mmap_no_write = yes protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=32765 gid=32765 home=/var/spool/postfix/var/mail/%u/./ } user = _dovecot-auth chroot = /var/spool/postfix } -----------------------------------------------------------

1 0

[Dovecot] whoson support
by Simon Dick 26 Apr '05

26 Apr '05

Is anyone working on integrating whoson support into dovecot? I would do it myself but currently I'm short on time and will need that support, anyone got any tips? :) -- Simon Dick <simon(a)advantage-interactive.com>

1 0

[Dovecot] 1.0-stable update
by Timo Sirainen 26 Apr '05

26 Apr '05

Just a note, I backported some larger mbox changes from 1.0-test67. Hopefully works, but if you're going to try it test it well first :) Should fix some issues related to X-IMAP/X-IMAPbase header handling and maybe some other mbox related problems as well.

3 6

[Dovecot] configuration problem: maildir folders and messages not found
by Bram Mertens 26 Apr '05

26 Apr '05

Hi Perhaps I've been going too far OT in my previous thread or perhaps I just didn't explain my problem clear enough so forgive me for trying again. I have configured fetchmail to fetch my mail from my ISP's POP3-server. I have set up procmail to filter messages and deliver all non-filtered messages to the folder ".IN-catchall/" in "$HOME/Maildir" After sending some test messages the "Maildir" folder in my home-folder looks like: m8ram@medion:~$ tree -a Maildir Maildir |-- .IN-catchall | |-- cur | |-- new | | `-- 1114356268.8424_0.medion | `-- tmp |-- .IN-testing | |-- cur | |-- new | | |-- 1114354955.6900_0.medion | | `-- 1114356175.8292_0.medion | `-- tmp |-- .INBOX | |-- .IN-testing | | |-- cur | | |-- new | | | |-- 1114354955.6900_0.medion | | | `-- 1114356175.8292_0.medion | | `-- tmp | |-- .imap.index | |-- .imap.index.data | |-- .imap.index.log | `-- .imap.index.tree |-- .customflags |-- IN-catchall |-- cur |-- new `-- tmp 16 directories, 11 files Because I have been using the mbox format to test dovecot so far I had to modify my dovecot configuration but no matter what I try none of the messages above appear in evolution or thunderbird. Can anybody tell me what I need to add/remove/change in my config? I'm running: m8ram@medion:~$ /usr/sbin/dovecot --version 0.99.14 on debian testing /etc/dovecot/dovecot.conf contains the following: protocols = imap login = imap login = pop3 mail_extra_groups = mail default_mail_env = maildir:/%h/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root When using mbox I used: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u I also tried the following for maildir: default_mail_env = maildir:~/Maildir default_mail_env = maildir:/home/%u/Maildir But neither worked. TIA Bram -- # Mertens Bram "M8ram" <bram-mertens(a)linux.be> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 13:39:03 up 30 days, 19:52, 13 users, load average: 0.49, 0.50, 0.39 #

2 4

[Dovecot] ldap uid with static gid problem
by Farkas Levente 26 Apr '05

26 Apr '05

hi, i'd like to use dovecot to authenticate from ldap. in ldap each user has it's uniq uid and gid. unfortunately with postfix we can't use uniq uid/gid since in this case we have ot create all user's home in advance. so we decided to use uniq uid and a common gid in postfix since in this case postfix can create new users maildir and deliver new mails. so i'd like to use everyone's own uid in dovecot, but a common gid (same as in postfix). but how can i do so? i read the wiki, but the problem is if i use: auth_userdb = ldap /etc/dovecot-ldap.conf then i have to define ldap attrib name in dovecot-ldap.conf: user_attrs = mail,,,uid,uidNumber,gidNumber what should i use in the last field in user_attrs? or it's not possible with dovecot to define this? i'd be very said in this case:-( any advice? thanks in advance. yours. -- Levente "Si vis pacem para bellum!"

2 1

[Dovecot] libexecdir and localstatedir problem
by Marten Lehmann 26 Apr '05

26 Apr '05

Hello, I'd really like to define the finale libexecdir and localstatedir through the configure-script. But the Makefiles are rewriting them. Not $libexecdir is used, but $pkglibexecdir. And $pkglibexecdir is always defined as $libexecdir/dovecot. But I don't want this trailing "/dovecot". Same with localstatedir. I want dovecot to use a certain path. But to this path, a "run/dovecot" is appended. I surely could build some patchfiles to change the Makefiles. But it would be easier, if you could add a new directive --pgklibexecdir to the configure-script. I don't know where the "run/dovecot" is defined, but it would also be very fine to set it in the configure-script (specially when upgrading to new releases) instead of defining them all in the dovecot.conf (base_dir, login_dir). Regards Marten

2 5

[Dovecot] 1.0-test68 released
by Timo Sirainen 26 Apr '05

26 Apr '05

http://dovecot.org/test/ Recommended update, has had a lot of testing today. No new big features. Changes: - LDAP authentication should work finally? - Some header lookup fixes that should fix sort/threading issues - Don't crash with 0-byte size mboxes - Transaction log fixes. Also rotate .log file to .log.2 file, allowing more history and less "transaction log file lost" messages. - SEARCHing multiple headers might have crashed - mbox: When first message was expunged we might have gotten "uid-last unexpectedly lost" errors. - recent flag counter wasn't updated in index file header always even if the recent flags were removed - UIDVALIDITY changes are handled more transparently - Added --rundir configure option (not actually tested, does it work? :) - etc.

6 12

[Dovecot] INBOX can't be deleted
by Marten Lehmann 26 Apr '05

26 Apr '05

Hi, surely it can't and it shouldn't. I'm just wondering why a check for "INBOX" is done in src/imap/cmd-delete.c AND src/lib-storage/index/maildir/maildir-storage.c. The first is clear because it gives an imap-error to the client. But for which case is the check in maildir-sorage.c? Just to be absolutely sure? The reason for me to ask is, because I need to disable deletions for five folders: Drafts, Infected, Junk, Sent and Trash. A certain webmail-interface and spamfilter will rely on these folders, so nobody shall be able to delete or rename them. First I placed the checks in cmd-delete.c. Should I place them in maildir-storage.c additionally? In normal circumstance, the check in maildir-storage.c should never be reached, right? Regards Marten

2 1

[Dovecot] Dovecot Stable (or: When is 1.0 coming to a server near you?)
by Rich West 26 Apr '05

26 Apr '05

I'm mainly just curious, but what version of dovecot is considered to be stable enough to be running in a production environment? We're running the 0.99.13 version shipped with FC3 and, while experiencing great performance gains over UW-IMAP, we have hit a couple of snags here and there (random and infrequent characters at the beginning of a mailbox, periodic duplication of a message here and there, etc). I figure we should upgrade to something a bit more current, but I am not sure what the "recommended" verion would be.. Also, perhaps more important, what's the roadmap to getting 1.0 finalized? What's the timeframe? :-) -Rich

2 1