- dovecot - dovecot.org

[Dovecot] (summarized) wishlist :-)
by Clemens Schrimpe 26 Nov '10

26 Nov '10

Hello All (and Timo in particular :-) -- While reading through some of the conversations on this list over the past two weeks or so, I always thought "how would <this> particular problem affect you and how would you address it in your environment?". This results in a few suggestions, or "thing to wish for", which I thought others may find useful, hence I'm posting this here. 1) the whole "post login scripting" is a mighty tool, yet it presently lacks a few more words in the documentation, i.e., the syntax of the corresponding config files isn't /entirely/ clear to me. Yes, I can replay the examples given, but I'm not fully sure, what happens when, etc. I'm perfectly willing, though, to contribute to that, by documenting findings in the Wiki2 (I'm just using 2.0.x, sorry). I'd appreciate a few more examples, so if anyone has a funny, working configuration, making good use of "post login scripting", I'd appreciate it, if you'd "show" them! :-) Anyway: A bit more "control" over PLS would be nice. For example, I'd like to have a script invoked every time a new "session" starts (new IMAP/POP3 connection from a unique ID), as many clients open multiple connections at once and usually I wouldn't want to see the second, third, nth connection - just the first. "Nice" would also a "post logout scripting" feature - again: Both for "all" connections, as well as just for the "last" one. Yes, this certainly requires a bit more discussion, I know - but I hope to trigger just that with this message! :-) 2) The "local x.x.x.x {" feature is very nice, yet it could use some "polishing", I guess. Inclusion of ports and wildcards for either addresses or ports, for instance. I'm imagining a syntax like this: local 1.2.3.4 { ... } like now to remain backward compatible local 1.2.3.4:* { ... } same result, just different new syntax -> don't care about port local 1.2.3.4:4711 { ... } add port restriction local *:4711 { ... } don't care for address, but match on port and -of course- (yes, I am really USING IPv6), the use of "[2001:xxxx:yyyy::zzzz]" instead of "1.2.3.4" in the examples show above. If one would like to become really funky, the optional "/xx" addition to specify a prefix-length would leave no more wishes open. (Well ... maybe the use of "names" derived from DNS instead of literal addresses, of course :-) [if this feature becomes clearer to me, I'd -again- be happy to help document it within the Wiki2] 3) The "iterate_query" in the SQL interface (I assume, there is something similar in the LDAP realm?) could be supplied with a few (optional, of course) "%x" variables, i.e., "%s" could deliver the "service" again, like with the other queries. This could tell the database engine, what the "show me all users" query is being used for ("quota", "expunge", ... basically all functions of doveadm, where you can supply a "-A" parameter). A "%{env:HOST}" could be used to tell the DB interface, which node of a multi-node installation is "asking". I.e., if you have your users distributed over multiple nodes, each one might want to perform "cleanups" only for their own users, saving a lot of bandwidth for unnecessary NFS traffic, etc. That's it - for now. Otherwise I'm pretty happy with dovecot, let me make that very clear here! :-) :-) :-) Clemens

2 1

[Dovecot] ioloop.c panic
by Brad Davidson 26 Nov '10

26 Nov '10

Timo, Just this morning I upgraded from 2.0.6 to 2.0.7 (hg changeset 66a523135836). A few hours later we had some power problems that caused the networking to drop out at one site. The directors on the surviving site all had a few imap-login processes crash with the following error: Nov 23 09:15:30 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) Nov 23 09:15:31 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) Nov 23 09:55:48 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) Nov 23 09:55:51 cc-director2 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) I don't have core dumps enabled, so I can't provide any more information than that. I could enable cores, but I honestly would be hard-pressed to replicate the network cut-out anyway so I'm not optimistic that any cores for this message would ever be forthcoming. Thanks, -Brad --- Brandon 'Brad' Davidson Virtualization Systems Administrator University of Oregon Information Services (541) 346-8098 brandond(a)uoregon.edu

2 1

[Dovecot] ldap passdb + mdbox
by Daniel L. Miller 26 Nov '10

26 Nov '10

I previously had a static userdb and an ldap passdb. Everything's been working fine, both 1.2 and 2.0 - but now I need to support the nightly mdbox purge operation. I added the iterate params to my ldap configuration, but (I'm guessing) that with a defined static userdb it won't work. How should I setup my ldap userdb? Do I use prefetch? Current config: passdb { driver = ldap args = /usr/local/etc/dovecot/dovecot-ldap.conf } userdb { driver = static args = uid=vmail gid=mail home=/var/mail/%d/%n mail=mdbox:/var/mail/%d/%n/mdbox allow_all_users=yes } dovecot-ldap.conf: ## dn credentials shouldn't be needed since using auth-bind - but here anyway dn = xxx,dc=amfeslan,dc=local dnpass = xxx ## auth_bind = yes auth_bind_userdn = uid=%n,ou=users,dc=amfeslan,dc=local ldap_version = 3 base = ou=Users, dc=amfeslan, dc=local user_attrs = dbox:%d/%n/Maildir=mail,%d/%n=home user_filter = (mail=%u) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=inetOrgPerson)(mail=%u)) iterate_attrs = mail=user iterate_filter = (&(objectClass=inetOrgPerson)(mail=*)) -- Daniel

3 7

[Dovecot] auth on tcp socket?
by Hajo Locke 26 Nov '10

26 Nov '10

Hello, is it possible to provide service auth on tcp-socket instead of unix-socket? I changed my conf and dovecot 2.0.5 is restarting but on telnet test it throws: dovecot: auth: Fatal: getsockname(12) failed: Socket operation on non-socket Want to separate smtp and imap to different servers but keep using dovecot auth for postfix-sasl. Whats to do? hmm, is postfix able to use non-unix socket for dovecot-sasl? Thanks, Hajo

2 1

[Dovecot] proxy (director) and destination ports
by Oliver Eales 26 Nov '10

26 Nov '10

Hello, i am delivering Mail from postfix via LMTP to dovecot. I am using the director also for LMTP. As long as i connect to the dovecot LMTP TCP socket from postfix everything is working. postfix main.cf: virtual_transport= lmtp:localhost:30025 But when i try to switch to the local socket postfix main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp The dovecot proxy tries to connect to the backend server port 0 which is obviously not working. The proxy always seems to connect to the same port on the backend as it was accessed itself. Nov 24 14:55:09 auth: Debug: master out: PASS 1 user=1000000000030 proxy Nov 24 14:55:09 lmtp(7330): Debug: auth input: user=1000000000030 proxy host=10.1.1.151 proxy_refresh=450 Nov 24 14:55:09 lmtp(7330): Error: lmtp client: connect(10.1.1.151, 0) failed: Connection refused Nov 24 14:55:11 director: Error: director(15.189.34.59:13459/out): connect() failed: Connection refused Is it possible to set the destination port (30025) of the backend server to the proxy ? Regards, Oliver

2 1

[Dovecot] Director
by Diego Damian Garcia 26 Nov '10

26 Nov '10

Hi. I am try to setup director in dovecot 2.0.7-1_123 but I don´t unserstand how this work. Have any tutorial with instructions to setup the director to autenticate users and send to the real mail servers? Sincerely Thanks. Diego.

2 1

[Dovecot] Director and deliver
by Thomas Hummel 26 Nov '10

26 Nov '10

Hello Timo, Although I haven't tried neither director nor deliver, I'm planning to try both. I've been catching up with threads on this list talking about director but I'm not sure about how deliver would fit into a setup using director. Since deliver would touch indexes and dovecot-uidlist, wouldn't it need to be proxied as well through director ? Is that the case ? If not, how can we use deliver as LDA in a setup where n directors would proxy to m dovecot backends ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

3 6

[Dovecot] maildir maintenance?
by Brian Kroth 26 Nov '10

26 Nov '10

Hi, I'm running version 1.2.15 (so no doveadm) with around 6000 maildir users, some of which are very large. For completeness, the details of the setup are as follows: - The maildirs are stored via NFS. - The indexes are on a volume local to the dovecot server. - Only one IMAP server currently. - A separate sendmail/procmail server delivers via NFS. I recently wrote the attached script (could probably be improved) meant in theory to be run as a nightly cron job to do the follow: 1) Remove old messages marked as deleted. (I didn't really like the expunge/trash plugins the last time I looked at them.) 2) Rebuild the indexes to account of those changes. (So that the users aren't delayed by dovecot rebuilding them.) 3) Rebuild FTS indexes. (Again to avoid delay.) 4) Rebuild the maildirsize file. (It seems to become slightly inaccurate over time.) To the devs, I'm wondering if this seems sane? To other users of dovecot, I'm wondering what, if any sort of maintenance operations you tend to do in your setups? Thanks, Brian

3 8

[Dovecot] Quota by max file size
by Antonio Perez-Aranda 26 Nov '10

26 Nov '10

Is It possible have a quota for max file size? Per example, If the client try to save a very big mail as draft, p.e. 100M, and the limit of Exim configuration is 20M, the mail is really saved in Maildir at sent or Draft but it can't be sent. I think maybe is easy to create a plugin, get the saved stream size and then if it is over quota max file size, abort save and notice to use about the limit, but at first I want to know that really daesn't similar exists.

2 1

[Dovecot] iPhone leaves imap process active
by Jim 26 Nov '10

26 Nov '10

A quick search of the archives didn't reveal a fix, so I thought I'd ask the list. I was running Dovecot 2.0.2, and noticed a lot of CPU being used up. I discovered a number of IMAP processes burning a lot of cycles, when no connections should have been active. I traced this to the iPhone leaving the IMAP connection apparently active. I just upgraded to Dovecot 2.0.7, and I'm still seeing connections left active, but haven't seen the high CPU usage yet, but I've only been running 2.0.7 for about 30 minutes. I tried adding kill_idle to the IMAP config, but that doesn't seem to have helped. Turning off the iPhone does kill the connection, so I know that the iPhone is really keeping the connection alive, but if I can find a way to keep these connections down, I'd really rather have that ability. Here's my config: wrights-Mac-mini:/Users/transmit wright$ doveconf -n # 2.0.7: /usr/local/etc/dovecot/dovecot.conf # OS: Darwin 10.4.0 i386 hfs auth_mechanisms = plain login cram-md5 default_internal_user = _dovecot disable_plaintext_auth = no first_valid_gid = 27 first_valid_uid = 27 last_valid_gid = 27 last_valid_uid = 27 mail_gid = 27 mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = postfix mail_uid = 27 namespace { inbox = yes location = prefix = type = private } passdb { args = /usr/local/etc/dovecot-mysql.conf driver = sql } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { process_limit = 64 } service imap { idle_kill = 150 secs process_limit = 128 } service pop3-login { process_limit = 64 } service pop3 { process_limit = 128 } ssl = no userdb { args = /usr/local/etc/dovecot-mysql.conf driver = sql } protocol lda { postmaster_address = postmaster(a)example.com } wrights-Mac-mini:/Users/transmit wright$

2 1