- dovecot - dovecot.org

[Dovecot] Permissions problems
by Google 27 Nov '13

27 Nov '13

Hi, I have dovecot 2.0.20 running (its an old version, I know, it came from the stable archive at OpenCSW) with Solaris SMF integration working fine. It enables and disables okay. However, I cantt connect to it, it is allowing the connection, but spewing on permissions: Nov 24 17:34:20 proliant-1 dovecot: [ID 583609 mail.info] master: Dovecot v2.0.20 starting up Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18816 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18818 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18820 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap(mark): Connection closed bytes=17/340 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.info] imap-login: Login: user=<mark>, method=PLAIN, rip=192.168.1.69, lip=192.168.1.72, mpid=18822 Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot.index.log.newlock, /mpool/mail/mark/dovecot.index.log) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: rename(/mpool/mail/mark/dovecot-uidlist.tmp, /mpool/mail/mark/dovecot-uidlist) failed: Permission denied Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: unlink(/mpool/mail/mark/dovecot-uidlist.tmp) failed: Permission denied If I actually try to copy mail to the inbox of the account it core-dumps and does, and the SMF service drops into maintenance mode which requires re-enabling. The output from doveconf -n (this is changes from the default settings I think?) is: root@proliant-1:~# doveconf -n # 2.0.20: /etc/opt/csw/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc zfs auth_first_valid_uid = 101 disable_plaintext_auth = no first_valid_uid = 101 mail_location = maildir:/mpool/mail/%u passdb { driver = pam } ssl_cert = </opt/csw/ssl/certs/dovecot.pem ssl_key = </opt/csw/ssl/private/dovecot.pem userdb { driver = passwd } The mail_location is in a ZFS filesystem on my RAIDz array. I couldnt think of any other way of creating user-specific folders in the location. As the value suggests, each user gets their own directory on the filesystem for mail. Is this still a ‘safe’ way to do things or would I be better off relocating each user’s ‘home’ directory to the pool somehow? This is what the directory currently looks like: mark@proliant-1:~$ ls -la /mpool/mail total 6 drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 . drwxr-xr-x+ 5 root root 5 2013-11-24 13:50 .. drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 mark mark@proliant-1:~$ ls -la /mpool/mail/mark/ total 14 drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 . drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 .. drwxrwxrwx+ 2 mark staff 2 2013-11-24 17:17 cur -rwxrwxrwx+ 1 mark staff 51 2013-11-24 22:20 dovecot-uidlist.tmp -rwxrwxrwx+ 1 mark staff 8 2013-11-24 22:20 dovecot-uidvalidity -rwxrwxrwx+ 1 mark staff 0 2013-11-24 17:17 dovecot-uidvalidity.529234ad -rwxrwxrwx+ 1 mark staff 40 2013-11-24 22:20 dovecot.index.log.newlock drwxrwxrwx+ 2 mark staff 2 2013-11-24 17:17 new drwxrwxrwx+ 2 mark staff 3 2013-11-24 17:21 tmp Any ideas? -- Mark Benson http://DECtec.info Twitter: @DECtecInfo HECnet: STAR69::MARK Online Resource & Mailing List for DEC Enthusiasts.

3 2

[Dovecot] Dovecot 2.1.16
by paolo.brocchi 27 Nov '13

27 Nov '13

Hi, i would ask you a question about a particular dovecot configuration. I would like to have in INBOX folder some emails (e.g email with a header key). The same emails i would like to have into the folders, under INBOX, create by users. How can i do? Thanks Paolo

2 4

[Dovecot] Dovecot 2.1 Panic
by Alexandr Sabitov 27 Nov '13

27 Nov '13

Hi, Dovecot 2.1.12 sends panic message when it tries to authenticate some users. Apparently because they use different authentication mechanisms on different email clients at the same time. For example, in debug logs this user uses CRAM-MD5, NTLM and PLAIN in account settings of his email clients. All passwords are stored in plain text (base64) in LDAP. Please advise me what I can tweak to fix this issue ? Nov 27 06:38:36 dovecot-1 auth: Error: ldap(gone(a)in.com.au,201.45.21.151,<qZlhoBnsvQDLLRuX>): Multiple password values not supported Nov 27 06:38:36 dovecot-1 auth: Panic: file passdb-ldap.c: line 95 (ldap_lookup_finish): assertion failed: (password == NULL || scheme != NULL) Nov 27 06:38:36 dovecot-1 auth: Error: ldap(gone(a)in.com.au,201.45.21.151,<qZlhoBnsvQDLLRuX>): Multiple password values not supported Nov 27 06:38:36 dovecot-1 auth: Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x485ca) [0x7f90ed51b5ca] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x48616) [0x7f90ed51b616] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f90ed4eeeef] -> dovecot-proxy/auth() [0x42967c] -> dovecot-proxy/auth() [0x428da1] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f90ed5277a6] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f90ed5287df] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f90ed527748] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f90ed513123] -> dovecot-proxy/auth(main+0x376) [0x41bd26] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f90ec2d8c8d] -> dovecot-proxy/auth() [0x40d0f9] Nov 27 06:38:36 dovecot-1 auth: Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x485ca) [0x7f90ed51b5ca] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x48616) [0x7f90ed51b616] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f90ed4eeeef] -> dovecot-proxy/auth() [0x42967c] -> dovecot-proxy/auth() [0x428da1] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f90ed5277a6] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f90ed5287df] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f90ed527748] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f90ed513123] -> dovecot- proxy/auth(main+0x376) [0x41bd26] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f90ec2d8c8d] -> dovecot-proxy/auth() [0x40d0f9] Nov 27 06:38:36 dovecot-1 director: Error: Auth server disconnected unexpectedly Nov 27 06:38:36 dovecot-1 auth: Fatal: master: service(auth): child 26841 killed with signal 6 (core dumps disabled) This is LDAP configuration on one of director servers where clients are authenticated. uris = ldap://ldap-node-2.mynetwork.net, ldap://ldap-node-3.mynetwork.net debug_level = 0 base = ou=email, dc=netregistry, dc=net user_attrs = homeDirectory=home, uidNumber=uid, gidNumber=gid, mailQuotaSize=quota_rule=*:storage=%$ user_filter = (&(objectClass=nrPOPAccount)(uid=%u)) pass_attrs = uid=user, userPassword=password, =proxy=y, =destuser=%u, =pass=Secret456 pass_filter = (&(objectClass=nrPOPAccount)(uid=%u)) default_pass_scheme = PLAIN Regards, Alexandr Sabitov System Administrator

1 0

[Dovecot] Dovecot software testing and release practice
by Andreas Kasenides 26 Nov '13

26 Nov '13

Since this, it seems, was lost in, the now infamous, 2.2.9 thread I would like to resubmit the following proposal for Timo's consideration. Thanks Timo for doing an excellent job. I believe that the following will add further value to Dovecot in the long run. Thankx Andreas ============================ > On 23-11-2013 3:47, Noel Butler wrote: > > On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: > * Thomas Leuxner <tlx(a)leuxner.net>: > * Ralf Hildebrandt <Ralf.Hildebrandt(a)charite.de> 2013.11.22 > 09:44: > > Which patch? > > > http://www.dovecot.org/list/dovecot/2013-November/093654.html > Pigeonhole related patches. > Damn. Those are biting me as well :/ > > These would be found if Timo reverted back to issuing RC's before any > official release, to iron out the > niggly off-putting bugs, like most software does, or gets his devs and > a community of official > >testers>each with wildly different > configurations and set ups, ASF have an excellent model that could be > >followed, >bunch of devs and testers who each report on different distros and configs, why? because no >single dev can imagine and test every possible configuration. it might just save dovecot's good name, I >recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly >every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because >major bugs were getting in often, though it has been a lot better since 2.1 series, until this release >that is :) I second this and offer my services for two, three different system configs from Dovecot's plain old simple config with MAILDIR to slightly more complicated configurations with proxying/LDAP/dsync/mySQL etc based on virtualization with KVM. I also propose that upon employing above strategy that Timo should come up with a release cycles (long term, short term) with announced targets. Patches should be released as patches strictly as needed, not releases, and should be announced on a low traffic list like he is already doing with releases. OR something along these lines. I know these are growing pains but essential. Email systems are CRITICAL for most of us. Andreas

1 0

[Dovecot] Replication master/master
by John Smith 26 Nov '13

26 Nov '13

Hello, i need help for this error: "dovecot: replicator: Error: Invalid replicator db record:" my config http://pastebin.com/jVnvyWZM -- Best Regards, Evgeny Senior System Administrator OOO "Vaz Service Hurley"

1 0

[Dovecot] Problem with Thunderbird and mailbox with SPECIAL-USE flag
by Sylvain 26 Nov '13

26 Nov '13

Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with the great Dovecot. SOGo webmail is connected to the proxy and works great (very very more fast) but I have a problem with Thunderbird : mailbox with « SPECIAL USE » aren't automatically detected. To make that works, I must : - in Dovecot : define the namespace inbox : « prefix = » and « separator = . » - in Thunderbird : force in the account, the personal namespace to "INBOX." and untick « Allow server to exceed namespace » (sorry : personal translation :D). If I define in the namespace inbox as the dovecot wiki said : « prefix = INBOX. » and « separator = . », TB see a sub-folder INBOX and mailbox with special use aren't automatically detected. :-( I must have forgotten a parameter in my Dovecot configuration but I don't see it.. Can you have a look please ? Here my configuration : # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_debug_passwords = yes auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 100 imapc_host = xxxxxx mail_gid = imapproxy mail_home = /var/local/cache/dovecot/%1Mu/%1.1Mu/%u mail_location = imapc:~/imapc mail_uid = imapproxy namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . type = private } passdb { args = host=xxxxxx port=143 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } protocols = imap ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } Sylvain

1 1

[Dovecot] 2.2.9
by Nick Edwards 26 Nov '13

26 Nov '13

Timo (since he is the only one that maters here), In past couple of days I have seen 4 people on IRC bitten by 2.2.8 and pigeonhole bug, none of them are on this list, so like all others who want to download and build them, are unaware of the patch, so, given how wide the userbase is with pigeonhole sieve and dovecot, this would or should be considered a serious bug, so my question is Timo, is it not best to immediately push 2.2.9, or should even more server administrators become frustrated and curse waiting two more months until you have a list you think is best putting out a new release, many of them dont like the constant new releases all the time with only minor things, but with a build failure, thats a serious issue.

15 27

Re: [Dovecot] 2.2.9
by Rick Romero 26 Nov '13

26 Nov '13

Noel, I include you in the gang of three, and I only read half the posts on this list. I have no specific reason to, but it isn't a good association. A decade ago I was active on the Pegasus mail and Mercury lists, and names stood out after a while. Unfortunately on this list, the names stand out for a completely different reason - and its not positive. Just chill, everyone. You never know who's going to interview you in a year. Rick

2 1

[Dovecot] postfix and dovecot - no emails in new folder
by Don Hill 26 Nov '13

26 Nov '13

Hi. I am working on setting up Dovecot v2.0.9 and postfix 2.6.6 on centos 6.4. I have postfix configured with dovecot using virtual users. Everything seems to be working with the exception of no emails being delivered to the Maildir/new folder. If I touch a file into that folder then the file gets delivered to the email client using imap. I can also send email from the client with no problems. In fact if I look at the logs postfix says the email was delivered to the mailbox. postfix/virtual[27270]: 8652F35C38A8: to=<user(a)domain.tld>, relay=virtual, delay=0.11, delays=0.1/0.01/0/0, dsn=2.0.0, status=sent (delivered to mailbox)$ Here is my dovecot -n output *doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf** **doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } }** **# OS: Linux 2.6.32-042stab079.6 x86_64 CentOS release 6.4 (Final) reiserfs** **auth_mechanisms = plain login** **default_login_user = vmail** **first_valid_gid = 5000** **first_valid_uid = 5000** **listen = *** **mail_access_groups = vmail** **mail_location = maildir:/var/vmail/%d/%u/Maildir** **mbox_write_locks = fcntl** **passdb {** ** args = scheme=SHA1 /etc/dovecot/passwd** ** driver = passwd-file** **}** **protocols = imap pop3** **service auth {** ** unix_listener auth-client {** ** group = postfix** ** mode = 0660** ** user = postfix** ** }** ** user = root** **}** **service imap-login {** ** inet_listener imaps {** ** address = *** ** }** ** process_min_avail = 1** ** user = vmail** **}** **service pop3-login {** ** inet_listener pop3s {** ** address = *** ** }** **}** **ssl_cert = </etc/pki/dovecot/certs/dovecot.pem** **ssl_key = </etc/pki/dovecot/private/dovecot.pem** **userdb {** ** args = uid=5000 gid=5000 home=/var/vmail/%d/%u allow_all_users=yes** ** driver = static** **}* Any thoughts?

4 7

[Dovecot] Invitation to connect on LinkedIn
by Don Hill 26 Nov '13

26 Nov '13

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Don Don Hill Senior Technical Consultant at Lincoln Financial Group Greater Chicago Area Confirm that you know Don Hill: https://www.linkedin.com/e/458g9e-hogi596x-46/isd/18305189187/jxXw8l7X/?hs=… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/458g9e-hogi596x-46/V7LnuFRIQXpYNGb2yum6IE4IQU3ZkP… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0