April 2012 - dovecot - dovecot.org

[Dovecot] Troubles with /.dovecot.lda-dupe on dovecot 2.1.5
by Jean Michel 26 Apr '12

26 Apr '12

Seems that is something with vacation message, Apr 26 12:20:02 server dovecot: lmtp(26937, user@domain): Error: file_dotlock_create(/storage/domain/users/user/.dovecot.lda-dupes) failed: Resource temporarily unavailable Apr 26 12:20:02 server dovecot: lmtp(26937, user@domain): Fatal: master: service(lmtp): child 26937 killed with signal 11 (core dumps disabled) And its created a .dovecot.lda-dupes.lock Any idea ? -- ------------------------------ Jean Michel Feltrin

2 1

[Dovecot] LDA crashes on delivery (using sieve)
by interfaSys sàrl 26 Apr '12

26 Apr '12

Hello, The current version of LDA can crash (seg fault 11) under certain circumstances. I don't know why it happens only with some accounts, but here is a backtrace. The user has a sieve filter in place : (gdb) bt full #0 0x0000000800443434 in smtp_client_open () from /usr/lib/dovecot/libdovecot-lda.so.0 No symbol table info available. #1 0x00000008009943ab in lda_sieve_smtp_open.2406.2210 () from /usr/lib/dovecot/lib90_sieve_plugin.so No symbol table info available. #2 0x0000000800e80532 in sieve_smtp_open () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #3 0x0000000800e6157d in act_redirect_send.23018 () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #4 0x0000000800e7e175 in act_redirect_commit.23025 () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #5 0x0000000800e5f2bd in sieve_result_execute () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #6 0x0000000800e5ee7b in sieve_multiscript_execute.25305 () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #7 0x0000000800e496f8 in sieve_multiscript_run () from /usr/lib/dovecot/libdovecot-sieve.so.0 No symbol table info available. #8 0x0000000800994652 in lda_sieve_multiscript_execute.2399.2297 () from /usr/lib/dovecot/lib90_sieve_plugin.so No symbol table info available. #9 0x00000008009942c7 in lda_sieve_deliver_mail.2402.2206 () from /usr/lib/dovecot/lib90_sieve_plugin.so No symbol table info available. #10 0x00000008004435d8 in mail_deliver () from /usr/lib/dovecot/libdovecot-lda.so.0 No symbol table info available. #11 0x00000000004029f7 in main (argc=7, argv=0x7fffffffe830) at main.c:434 set_roots = {0x404520, 0x0} ctx = {pool = 0x800a0d820, set = 0x800a3cc98, session = 0x800a0d840, dup_ctx = 0x800abf0c0, session_id = 0x0, src_mail = 0x800a34840, src_envelope_sender = 0x800a0d858 "mailtest(a)example.com", dest_user = 0x800a89040, dest_addr = 0x7fffffffebfd "test(a)example.com", final_dest_addr = 0x7fffffffebfd "test(a)example.com", dest_mailbox_name = 0x40356b "INBOX", dest_mail = 0x0, var_expand_table = 0x0, tried_default_save = false, saved_mail = false, save_dest_mail = false, mailbox_full = false, dsn = false} service_flags = 1027 user = (const __unknown__ *) 0x7fffffffebcc "test(a)example.com" errstr = (const __unknown__ *) 0x0 path = (const __unknown__ *) 0x0 storage_service = (struct mail_storage_service_ctx *) 0x800a30840 service_user = (struct mail_storage_service_user *) 0x800a3c0a0 service_input = {module = 0x403567 "lda", service = 0x403567 "lda", username = 0x7fffffffebcc "test(a)example.com", session_id = 0x0, local_ip = {family = 0, u = {ip6 = {__u6_addr = {__u6_addr8 = '\0' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = { s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__u6_addr = {__u6_addr8 = '\0' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = 0, flags_override_remove = 0, no_userdb_lookup = 0} storage = (struct mail_storage *) 0x0 user_source = (const __unknown__ *) 0x4034c0 "" destaddr_source = (const __unknown__ *) 0x403576 "-a parameter" process_euid = 0 stderr_rejection = false ret = 1 c = -1 error = MAIL_ERROR_NONE Cheers, Olivier

1 0

[Dovecot] dovecot 2:2.1.5-0~auto+6 on debian squeeze
by Tomislav Mihalicek 26 Apr '12

26 Apr '12

After upgrade from latest 2.1.4 to 2.1.5 occasional coredumps on lmtp/lda daemon happens. It results in deffering mail in previous hop server and mail delay [1383350.925251] lmtp[22130]: segfault at 0 ip 00007f8829e2b4c5 sp 00007fff29fd37e0 error 4 in libdovecot-lda.so.0.0.0[7f8829e23000+b000] [1383351.038095] lmtp[22121]: segfault at 0 ip 00007f18863084c5 sp 00007fff65d87b20 error 4 in libdovecot-lda.so.0.0.0[7f1886300000+b000] [1383366.682285] lmtp[22101]: segfault at 0 ip 00007fe87a36a4c5 sp 00007fffb391b430 error 4 in libdovecot-lda.so.0.0.0[7fe87a362000+b000] [1383530.705974] lmtp[22126]: segfault at 0 ip 00007f0a7caa74c5 sp 00007ffff5bd0050 error 4 in libdovecot-lda.so.0.0.0[7f0a7ca9f000+b000] [1383530.844101] lmtp[17613]: segfault at 0 ip 00007f43aa1e84c5 sp 00007fff977ffd70 error 4 in libdovecot-lda.so.0.0.0[7f43aa1e0000+b000] [1383544.463542] lmtp[17576]: segfault at 0 ip 00007fbec6bc64c5 sp 00007fff3e347910 error 4 in libdovecot-lda.so.0.0.0[7fbec6bbe000+b000] -- View this message in context: http://old.nabble.com/dovecot-2%3A2.1.5-0%7Eauto%2B6-on-debian-squeeze-tp33… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] Permission problems when trying to create new folders with ACL plugin
by Markus Petri 26 Apr '12

26 Apr '12

Hi, I have the a problem with shared folders and the ACL plugin. The user "markus" has full access to "Shared/shared-user/Data": 3 GETACL "Shared/shared-user/Data" * ACL "Shared/shared-user/Data" "markus" akxeilprwtscd 3 OK Getacl completed. but creating a new subfolder under "Data" fails: 4 CREATE "Shared/shared-user/Data/New1" 4 NO [NOPERM] Permission denied This used to work with the same configuration and Dovecot 2.0. Cheers, Markus dovecot -n output: # 2.1.5: /opt/dovecot-2.1/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-2-amd64 x86_64 Debian wheezy/sid auth_mechanisms = plain login disable_plaintext_auth = no listen = 192.168.56.11 mail_location = maildir:~/Maildir mail_plugins = acl 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 namespace { inbox = yes location = prefix = separator = / subscriptions = yes type = private } namespace { inbox = no list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/index/shared/%%u prefix = Shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/vdovecot/shared-mailboxes.db } protocols = imap service auth { unix_listener auth-userdb { mode = 0600 user = vdovecot } } ssl = no userdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = acl imap_acl }

2 2

[Dovecot] v2.1.5 released
by Timo Sirainen 26 Apr '12

26 Apr '12

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as well, so they just waste my time. Even if you're sure that I'm the only person who can possibly answer it, it may be something that others are interested of as well and replying privately denies them the possibility of reading about it. If you really do not want to send something publicly, you still have an option for private communication: just buy one of the Dovecot support packages. This is also the first Dovecot release that has run through automated release testing. I've been planning on doing that for last 5 years at least, and finally it's done. The testing includes running a lot of tests to verify that the IMAP server gives proper responses, stress testing doesn't break it, memory isn't leaked and several other things. The tests are run for many different kinds of configurations. Some bugs show up only for some specific combination of settings, but unfortunately because there's such a large number of them it's impossible to test every combination. So here's another advantage that Dovecot support customers have: they can have their specific configuration included in the automated tests. This release already fixes one bug I found only after testing a customer's config. Oh, and looks like I got accepted as a speaker to LinuxTag 2012. The plan is to talk about some new things in Dovecot and dsync replication (looks like I have to hurry up with the dsync rewrite). And finally, the most important changes since v2.1.4: * IMAP: When neither the session nor the mailbox has modseq tracking enabled, return the mailbox as having NOMODSEQ in SELECT/EXAMINE reply. Old versions in this situation always simply returned HIGHESTMODSEQ as 1, which could have broken some clients. + dict file: Added optional fcntl/flock locking (default is dotlock) + fts-solr: doveadm fts rescan now resets indexes, which allows reindexing mails. (This isn't a full rescan implementation like fts-lucene has.) + doveadm expunge: Added -d parameter to delete mailbox if it's empty after expunging. - IMAP: Several fixes related to mailbox listing in some configs - director: A lot of fixes and performance improvements - v2.1.4 didn't work without a mail home directory set - mbox: Deleting a mailbox didn't delete its index files. - pop3c: TOP command was sent incorrectly - trash plugin didn't work properly - LMTP: Don't add a duplicate Return-Path: header when proxying. - listescape: Don't unescape namespace prefixes.

8 13

[Dovecot] LDAP Lookup not returning value in maxStorage
by Bruce, Andrew 26 Apr '12

26 Apr '12

Hi there, We're setting up a Dovecot virtual email setup - we've got everything working perfect with LDAP logins authenticating against AD and so forth, but we're having issues with retrieving the maxStorage value from AD (this is a pre-setup field in AD that we'd like to use to set per user quotas). In our LDAP lookup, we have the maxStorage entry listed under user_attrs for the quota (user_attrs = maxStorage=quota_rule=*:storage=%$M), and in the debug logs, can see it trying to get the entry, but it fails with: Mar 27 13:19:27 auth: Debug: ldap(username(a)site,192.168.1.5): user search: base=dc=site,dc=local scope=subtree filter=(&(objectClass=person)(| (userPrincipalName=username@site) (|(mail=username@site)(samAccountName=username@site)))) fields=maxStorage Mar 27 13:19:27 auth: Debug: ldap(username(a)site,192.168.1.5): no fields returned by the server At this point, we then see the default quota applied. If we change the name of the field from maxStorage to instanceType we see the value show up in the logs and passed through to the quota system and applied successfully: Mar 27 11:09:01 auth: Debug: ldap(username(a)site,192.168.1.5): user search: base=dc=site,dc=local scope=subtree filter=(&(objectClass=person)(| (userPrincipalName=username@site) (|(mail=username@site)(samAccountName=username@site)))) fields=instanceType Mar 27 11:09:01 auth: Debug: ldap(username(a)site,192.168.1.5): result: instanceType(quota_rule=*:storage=%$M)=*:storage=4M Mar 27 11:09:01 auth: Debug: master out: USER 3901227009 username@site quota_rule=*:storage=4M Which seems a bit weird. If we use ldapsearch and pass it the same search string and look for the field maxStorage, we clearly see the field and the value being returned. The result looks the same if we also lookup instanceType. We're using Dovecot 2.0.9. Does anyone have any idea as to why we can't use this field? Thanks, Andrew

4 7

Re: [Dovecot] dovecot LDA with sendmail
by Joseph Tam 26 Apr '12

26 Apr '12

Timo, in response to Hadi, wrote: >> Apr 24 20:25:46 lda(jamal(a)example.com): Fatal: >> setgid(5000(vmail) from userdb lo >> okup) failed with >> euid=8(mail), gid=12(mail), egid=12(mail): Operation not permi >> tted (This binary should probably be called with process group set to 5000(vmail >> ) instead of 12(mail)) > > Configure your MTA to run dovecot-lda as vmail instead of as mail. Yeah, what he said. Someone helpfully added documentation on how to do this at the end of Dovecot1's wiki (http://wiki.dovecot.org/LDA/Sendmail) which probably should be copied to Dovecot 2's wiki. So that's what I did. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] dovecot %u variable problem....
by Kris 26 Apr '12

26 Apr '12

Hi guys n gals, im on an ubuntu 11 VPS on linode (dovecot version 2.013). ive spent a lot of time and googling trying to get postfix, dovecot, ssl, saslauthd and mysql to all play nice together and im quite close now but theres something going on i cant quite explain and id really appreciate some help. I have been going for ten hours on this today and it seems in direct conflict with what dovecot themselves say... the problem is a variable in dovecot (%u) which is normally used as a full username in sql query strings (i.e. user@domain) and is simply dropping the domain for some reason... From dovecot docs (http://wiki2.dovecot.org/Variables) The variables that work everywhere are: %u user full username (e.g. user@domain) so i have postfix and stuff set up ok to send at least and i know this because ive tested it by hard-coding the string in the sql query myself with a successful send... but, anyway, the problem with the '%u' variable is it is doing stuff like this: (from mail.log and mysql.log) localhost dovecot: auth: Debug: sql(admin(a)microhard.com,xx.xx.xx.xx): SELECT home,uid,gid FROM users WHERE id = 'admin(a)microhard.com' this was derived from the following query in /etc/dovecot/dovecot-sql.conf.ext user_query = SELECT home,uid,gid FROM users WHERE id = '%u' so no problem there.... but then this happens when i attempt to send mail and this means the user gets rejected because dovecot cant find the user id in the db without the correct string (i.e. user@domain): localhost dovecot: auth: Debug: sql(admin,xx.xx.xx.xx): query: SELECT id as user, crypt as password FROM users WHERE id= 'admin' Query SELECT id as user, crypt as password FROM users WHERE id= 'admin' which is derived from the following query also in /etc/dovecot/dovecot-sql.conf.ext password_query = SELECT id as user, crypt as password FROM users WHERE id= '%u' and to further confuse me, this 'unchangeable' variable sometimes decides to right itself without any obvious reason... localhost dovecot: auth: Debug: sql(admin(a)microhard.com,xx.xx.xx.xx): query: SELECT id as user, crypt as password FROM users WHERE id= 'admin(a)microhard.com' im wondering if its something to do with my client dropping the domain, or whether dovecot has an error, or some other thing ive overlooked... my dovecot.conf looks a lot like this: # 2.0.13: dovecot.conf # OS: Linux 3.0.18-x86_64-linode24 x86_64 Ubuntu 11.10 ext3 first_valid_uid = 5000 last_valid_uid = 5000 login_greeting = I likes my ducks n geese I do. mail_location = maildir:/var/spool/mail/virtual/%u #enables logging all failed authentication attempts. auth_verbose=yes #enables all authentication debug logging (also enables auth_verbose). Passwords are logged as <hidden>. auth_debug=yes #does everything that auth_debug=yes does, but it also removes password hiding. auth_debug_passwords=yes #enables all kinds of mail related debug logging, such as showing where Dovecot is looking for mails. mail_debug=yes #enables logging SSL errors and warnings. Even without this setting if connection is closed because of an SSL error, the error is logged as the disconnection reason (v1.1+). verbose_ssl=yes passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/etc/dovecot/acls #quota = maildir:storage=10240:messages=1000 trash = /etc/dovecot/trash.conf } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = dovecot mode = 0660 user = dovecot } user = dovecot } ssl_ca = /etc/pki/dovecot/certs/ca-bundle.crt ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { driver = prefetch } userdb { driver = passwd } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver.log mail_plugins = quota postmaster_address = admin(a)microhard.com } any help *much* appreciated! cheerz Kris

6 12

[Dovecot] dsync: convert only mbox in /var/mail to maildir?
by Jeff Simmons 26 Apr '12

26 Apr '12

I'm migrating an old UW pop server to a new Dovecot server. The old server did not allow mail to be stored on the server, so only mbox files exist in /var/mail, with nothing in /home/$user. I'd like to copy the /var/mail directory over to the new server and then use dsync to convert the mbox files and put them in /home/$user/Maildir, but every permutation of the command line I've tried dies with a variation on can't find/write either /var/mail/mail or /home/$user/mail, seems it won't deal with mbox files without an associated mail directory. Can dsync be used for this kind of conversion, or should I look elsewhere for conversion utilities? Thanks for helping a noob who can't traverse a wiki without leaving a trail of breadcrumbs. -- Jeff Simmons jeff(a)j-simmons.net Simmons Consulting - Network Engineering, Administration, Security

2 2

[Dovecot] 2.1.x changes and dsync -- Wiki suggestion
by Jeff Kletsky 26 Apr '12

26 Apr '12

There are a couple things that show up on the Upgrading/2.1 wiki page that would be useful to have on pages describing dsync (Tools/Dsync, Migration/MailFormat, Tools, perhaps others): * dsync was merged into doveadm * You can't dsync 2.0.x to/from 2.1.x That second point is especially "interesting" to me as it seems that Apple MacOS X Server is still on 2.0.16, at least from what I see on opensource.apple.com. I was planning on migrating mail off the current server onto my friend's new MacMini, but I'll have to figure out how to "downgrade" the mail jail to a 2.0 version, it seems. Thanks for all the great work, Jeff

1 0