- dovecot - dovecot.org

Re: [Dovecot] lmtp performance
by Juan Carlos Sanchez 04 Nov '11

04 Nov '11

A particular reply (not to the list) has told me to try: " Add to service lmtp: process_min_avail = 20 " And yes, it works (unless for me), so I want to share it with everybody. Have not exactly measured performance but this morning have seen over 1400 messages/minute with lmtp under heavy load. What the "process_min_avail = 20" in service lmtp (or anywhere else) exactly imply? cannot find a reference in wiki2 . I suppose it means than 20 lmtp processes are always open waiting for new connections and so reducing startup latency, isn't it? Thank you. > > On Mon, Oct 17, 2011 at 6:06 AM, Juan Carlos Sanchez > <juancarlos.sanchez(a)upm.es <mailto:juancarlos.sanchez@upm.es>> wrote: > > Hello: > > In the process of migration from version 1.2 to 2.0 have tried to > use lmtp instead of lda as delivery agent. > > But unfortunately througput we get is poor with lmtp compared to lda. > In peak times with lda we are able to deliver over 1800 > messages/minute (high I/O but not affecting service) but if we > switch to lmtp cannot deliver more than 300 mess/minute (very low > I/O). > > This is enough for normal work but low under heavy load > (distribution lists messages sometimes stay queued for 4 hours > before deliver). > > We have arround 50000 boxes and use postfix as MTA > > How to increase lmtp performance? > > > dovecot config for lda and lmtp: > > protocol lda { > auth_socket_path = /usr/local/var/run/dovecot/auth-master > info_log_path = /var/log/mail/dovecot_deliver.log > log_path = /var/log/mail/dovecot_deliver.log > mail_plugins = quota sieve zlib > postmaster_address = postmaster(a)upm.es <mailto:postmaster@upm.es> > sendmail_path = /usr/lib/sendmail > } > > protocol lmtp { > info_log_path = /var/log/mail/dovecot_deliver.log > log_path = /var/log/mail/dovecot_deliver.log > mail_plugins = quota sieve zlib > postmaster_address = postmaster(a)upm.es <mailto:postmaster@upm.es> > sendmail_path = /usr/lib/sendmail > } > > In postfix I have: > > mailbox_transport = lmtp:unix:private/dovecot-lmtp > > > > Thanks in advance. > > -- > > ------------------------------------------------------ > Juan Carlos Sanchez Hernandez > Universidad Politecnica de Madrid > ------------------------------------------------------ > > > -- ------------------------------------------------------ Juan Carlos Sanchez Hernandez Universidad Politecnica de Madrid ------------------------------------------------------

3 2

[Dovecot] imap proxy for Gmail
by Jumping Mouse 04 Nov '11

04 Nov '11

Hello, b I have a situation were I want to be able to give teachers access to their Google apps for education email through Squirrelmail. The network that they are on blocks gmail. I am able to get Squirrelmail to communicate with Gmail via imap. I am looking at getting persistant imap connections to improve the user experience. I have looked at IMAPPROXY but this application is not compatible with the gmail imaps (ssl-encrypted imap over port 993). I recall reading somewhere that Dovecot has a built in imapproxy that could be used for this. Can someone please point me to documentation or other information on how I might achieve the above stated goal? Thanks, Kafriki

3 2

[Dovecot] Proxy and Virtual IMAP Folders
by Pedro Paixao 04 Nov '11

04 Nov '11

Hi all I am a newbie to dovecot and I would like some help clarifying a feature to determine if I can use it in my project. Is is posible to use the virtual plugin, in a IMAP proxy configuration, in a way that the virtual plugin searches messages on the real server? Here's my scenario: [Client]----[Dovecot Proxy]-----[Real Imap Server] Client connects to Dovecot Proxy and gets all the folders that are on the Real Imap Server, plus some virtual ones (generated by Dovecot Proxy) that search for messages on the real server. In my config the Dovecot Proxy has no email messages, real folders, or local delivery. I would like to thank you in advance for ant help and support. All the best Pedro

2 1

[Dovecot] doveadm segfaults on TCP connect - version 2.0.15
by ghandidrivesahumvee＠rocketfish.com 04 Nov '11

04 Nov '11

Hi list, I just recently installed Dovecot 2.0.15. Unfortunately, doveadm segfaults when I attempt to connect to the local dovecot instance. When this occurs, my logs show: 2011-10-19T12:31:23-07:00 mail02 dovecot: doveadm: Error: doveadm client not compatible with this server (mixed old and new binaries?) I am using the settings listed on the wiki page http://wiki2.dovecot.org/Director [root@mail02 ~]# /opt/dovecot/bin/doveadm who -a 10.10.5.220:544 Segmentation fault (core dumped) doveconf and gdb output are below. If there is any more information I can provide please let me know. Thanks! [root@mail02 ~]# /opt/dovecot/bin/doveconf -n # 2.0.15: /opt/dovecot-2.0.15/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.17.4.el5 x86_64 CentOS release 5.5 (Final) auth_mechanisms = plain login auth_verbose = yes auth_worker_max_count = 60 default_client_limit = 2048 disable_plaintext_auth = no doveadm_proxy_port = 544 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 10.10.5.220, 127.0.0.1 lmtp_save_to_detail_mailbox = yes mail_fsync = always mail_log_prefix = "%r mpid=%p %s(%u): " mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " notify mail_log" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes passdb { args = /opt/dovecot/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete expunge mailbox_delete mail_log_fields = msgid box from mail_log_group_events = yes sieve = ~/MainSieve sieve_before = /storage03/sieve/before/ sieve_dir = ~/sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 2M } quota_full_tempfail = yes service anvil { client_limit = 2000 } service auth { client_limit = 7000 unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } unix_listener auth-userdb { group = mailowner mode = 0600 user = mailowner } } service doveadm { inet_listener { port = 544 } } service imap-login { inet_listener imap { port = 143 } process_min_avail = 4 service_count = 0 vsz_limit = 128 M } service imap {%0

5 6

[Dovecot] Rewrite the ostream output method, to save messages in another directory.
by Alex Baule 04 Nov '11

04 Nov '11

Hi Timo, I Trying to integrate my antispam with dovecot, using the imap folder to do certain actions. I Do almost every thing, but i have some problems saving the message. Explaining this function, i try to use a imap folder like a "collector folder", the user append a message from outside (ie another imap or pop message) to this folder, and i don't want to copy this message, i need to redirect it to another folder outside from user's maildir. Well, i try to base it in zlib plugin, with was the o_stream_create_gz(). Inside the o_stream_create_gz has the Output, it's a copy from the original output. I Try to replace this output, with another one, that i try to create to another location, without sucessfull. struct ostream * o_stream_create_X_list(struct ostream *output, struct istream *input, const char *type) { struct emexis_ostream *X_stream; struct ostream *new_output; int fd; fd = open("/tmp/email",O_WRONLY); new_output = o_stream_create_fd_file(fd, 0, TRUE); o_stream_cork(new_output); emexis_stream = i_new(struct emexis_ostream, 1); emexis_stream->ostream.sendv = o_stream_X_sendv; emexis_stream->ostream.flush = o_stream_X_flush; emexis_stream->ostream.iostream.close = o_stream_X_close; emexis_stream->output = new_output; emexis_stream->input = input; o_stream_ref(new_output); return o_stream_create(&X_stream->ostream); } With this new o_stream, i got this error. Oct 27 15:14:24 brc dovecot: imap(alex(a)exemplo.com.br): Error: o_stream_send_istream(/storage/gss/emexis/messages/ exemplo.com.br/alex/Maildir/.Emexis.Ext-Blacklist/tmp/1319735664.M568409P30815.brc) failed: Bad file descriptor Oct 27 15:14:24 brc dovecot: imap(alex(a)exemplo.com.br): Error: o_stream_flush(/storage/gss/emexis/messages/ exemplo.com.br/alex/Maildir/.Emexis.Ext-Blacklist/tmp/1319735664.M568409P30815.brc) failed: Bad file descriptor Oct 27 15:14:24 brc dovecot: imap(alex(a)exemplo.com.br): Error: write(/storage/gss/emexis/messages/ exemplo.com.br/alex/Maildir/.Emexis.Ext-Blacklist/tmp/1319735664.M568409P30815.brc) failed: Bad file descriptor There is something wrong Timo ? Like missing something or i need to rewrite another funcion ? Tks !!!

2 1

[Dovecot] doveadm delete-user ?
by Jan-Frode Myklebust 04 Nov '11

04 Nov '11

IMHO it would be great if we could both provision and un-provision users without having the provisioning system mess with files in the filesystem. Provisioning new users works fine since dovecot will create all files/directories on first login, but I haven´t found the tools to un-provison them. I see "doveadm mailbox delete" can delete individual mailboxes, but what about indexes, sieve-scripts and home-directories? Are there any tools to clean out these ? -jf

2 3

[Dovecot] Restricting IMAP access
by Thierry de Montaudry 04 Nov '11

04 Nov '11

Hi list, I have a setup with postfix+dovecot+mysql unser CentOS 5, running 50 odd domains with virtual users. Access is allowed for public POP3, and a webmail on apache+PHP solution through local IMAP. I'm not gonna give you the long story about the why, but I'm looking for a way to give public IMAP access only to one domain, knowing that users log in with full email (user(a)domain.tld) Anybody has a trick for that? Running dovecot 2.0.13. I know there should be a way to do it through the database, but quite heavy change on our side for a million odd users. Regards, Thierry

3 2

[Dovecot] Dot Lock timestmap, users disconnections from roundcube
by Maria Arrea 04 Nov '11

04 Nov '11

Hello. We are running dovecot 2.0.13 with mdbox+zlib on RHEL 5.7 x64, ext4. We use NTP. Indexes are in a iSCSI raid 10, mailboxes in raid5. No NFS. We have detected that sometimes all users get disconnected from roundcube at the same time. In dovecot logs we hundreds of lines like this: Nov 3 09:23:07 buzon dovecot: imap(mcrivero@mydomain): Warning: Created dotlock file's timestamp is different than current time (1320308587 vs 1320308542): /buzones/mydomain/03/67/mcrivero/subscriptions Nov 3 09:23:07 buzon dovecot: imap(mcrivero@mydomain): Connection closed bytes=0/295 Nov 3 09:23:07 buzon dovecot: imap(delolmo@mydomain): Warning: Created dotlock file's timestamp is different than current time (1320308587 vs 1320308542): /buzones/mydomain/15/77/delolmo/subscriptions Nov 3 09:23:07 buzon dovecot: imap(delolmo@mydomain): Connection closed bytes=0/295 I have been googling but I only see problems with remote NFS, our setup does not use NFS. I give you doveconf -n output & mount options, if more info es needed, please ask. doveconf -n output # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.el5 x86_64 Red Hat Enterprise Linux Server release 5.7 (Tikanga) ext4 auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_mechanisms = plain login auth_worker_max_count = 3500 base_dir = /var/run/dovecot/ default_client_limit = 5000 default_process_limit = 6500 disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_fsync = never mail_gid = entrega mail_home = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/ mail_location = mdbox:/buzones/mydomain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n mail_max_userip_connections = 15000 mail_plugins = " zlib acl quota autocreate" mail_uid = entrega managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mdbox_rotate_interval = 1 days mdbox_rotate_size = 60 M passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/usuario_maestro.txt driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile autocreate = SPAM autocreate2 = Sent autocreate3 = Drafts autocreate4 = Trash autosubscribe = SPAM autosubscribe2 = Sent autosubscribe3 = Drafts autosubscribe4 = Trash lda_mailbox_autosubscribe = yes quota = dict:Cuota de usuario::file:/buzones/cuotas/%n quota_rule2 = Trash:storage=+10%% quota_warning = storage=90%% aviso_cuota 90 %u sieve = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/dovecot.sieve sieve_dir = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/sieve/ zlib_save = gz zlib_save_level = 9 } pop3_no_flag_updates = yes protocols = pop3 imap sieve service anvil { client_limit = 25000 } service auth { client_limit = 28000 unix_listener auth-master { user = entrega } unix_listener auth-userdb { user = entrega } user = root } service aviso_cuota { executable = script /usr/local/bin/quota-warning.sh unix_listener aviso_cuota { mode = 0666 } user = entrega } service imap-login { executable = /usr/libexec/dovecot/imap-login group = dovenull service_count = 0 } service imap { executable = /usr/libexec/dovecot/imap process_limit = 6000 } service managesieve-login { executable = /usr/libexec/dovecot/managesieve-login inet_listener sieve { port = 2000 } process_limit = 2000 } service managesieve { executable = /usr/libexec/dovecot/managesieve process_limit = 5000 } service pop3-login { executable = /usr/libexec/dovecot/pop3-login process_limit = 4000 service_count = 0 } service pop3 { executable = /usr/libexec/dovecot/pop3 process_limit = 4000 } ssl_ca = </etc/pki/generico/cacert.crt.pem ssl_cert = </etc/pki/generico/wildcard-us_es.crt ssl_key = </etc/pki/generico/wildcard-key.pem userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } protocol lda { hostname = mydomain info_log_path = log_path = mail_fsync = optimized mail_plugins = sieve zlib quota postmaster_address = evcorreo@mydomain syslog_facility = mail } protocol imap { mail_plugins = zlib autocreate quota imap_quota } protocol pop3 { mail_plugins = zlib pop3_enable_last = yes pop3_uidl_format = %g } mount points: /dev/mapper/Volumen_0-Logico_0 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/mapper/Buzon_mydomain-buzones on /buzones type ext4 (rw,noatime,nodiratime,nobarrier,commit=15,data=writeback) Indexes are located somewhere in "/" mount point.

3 2

[Dovecot] IMP, Dovecot and multiple namespaces
by Rick Romero 04 Nov '11

04 Nov '11

Hey guys, I'm wondering what the best way is to be backwards compatible with Courier mailbox formats and not duplicate mailbox trees with Dovecot. Is anyone doing this right now? My Dovecot 2.0.13 is configured as follows for Namespaces: namespace { inbox = yes location = prefix = separator = . } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } So I should have an INBOX, plus additional root folders - rather than the Courier default of all folders being subfolders of the INBOX. So when I run LIST in IMAP I get - 08 LIST "" % * LIST (\HasChildren) "." "INBOX" * LIST (\HasChildren) "." "Spam" * LIST (\HasNoChildren) "." "Sent" * LIST (\HasNoChildren) "." "Trash" * LIST (\HasNoChildren) "." "Junk" * LIST (\HasNoChildren) "." "Drafts" Which looks fine. The problem is, IMP (old and new) show two sets of mailboxes (one for each namespace) like so: INBOX Spam Spam.Over10 Sent INBOX.Spam INBOX.Spam.Over10 INBOX.Sent (etc) I assume IMP is walking the INBOX because it says it has Children, and displaying those Children - The Horde team is telling me that's the root of the problem. It makes sense, but I'm not sure what the real solution is. Is it possible to disable Children for a mailbox when an alternate hidden namespace matches the mailbox name? Does that make sense? Or, is there another option I change change in the dovecot config to accomplish the same? Rick

2 1

[Dovecot] Different default realm per listener
by Kai Arif 04 Nov '11

04 Nov '11

Hi all! I want create a large IMAP server setup where dovecot is listening on multiple interfaces and needs a different default realm on each interface. I'm using dovecot 2.0.5 on FreeBSD9 and authenticate against a LDAP database. I found an old mail thread from 2007 that said I'm basically screwed. Has that change since than? Is there any way to use different default realms per listener? Best regards Kai -- Kai Arif - System Administrator Inter.net Germany GmbH Knesebeckstraße 59-61 10719 Berlin Germany Fon +49 30 25430 0 Fax +49 30 25430 499 arif(a)team.de.inter.net www.de.inter.net Legal-Information: Inter.net Germany GmbH, HRB #79136, Amtsgericht Berlin Charlottenburg, UST-IdNr:: DE 813 165 159 FA für Körperschaften I Berlin, Geschäftsführer: Jörn Lubkoll Zuständige Regulierungsbehörde: Bundesnetzagentur Chemnitz, Liselotte-Herrmann-Str. 20a, 09127 Chemnitz, Registriernummer: 06/164

2 1