- dovecot - dovecot.org

[Dovecot] How to grant a kerberos ticket after successful imap authentication from dovecot
by André Rodier 31 Mar '11

31 Mar '11

Hello everybody, I hope this question is appropriate for this list. Apologies if not. I am running a set of virtual machines under debian 6, to build a mail/collaboration server. I am mainly using dovecot, postfix, openldap and heimdal. Mails are stored using maildir, on a NFSv4 share. My users are system users, but using LDAP and libpam-ldap and libnss-ldap for caching credentials information. Everything is working as expected, well, /almost/. Since NFS is using kerberos, by defaults, my users are not able to access their mail storage if they have not received their kerberos ticket. For instance, if I do nothing, this is the errors I have from dovecot when trying to logon using any imap client: Mar 31 09:33:07 titan dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 31 09:33:07 titan dovecot: dovecot: Fatal: chdir(/home/emails/team/arodier/) failed: Permission denied (euid=1003(arodier) egid=1001(red2team) missing +x perm: /home/emails) Mar 31 09:33:07 titan dovecot: dovecot: child 5089 (imap) returned error 89 (Fatal failure) However, if I just login on a console for the user "/arodier/", I see that I have received a ticket, and I can see it with klist: Credentials cache: FILE:/tmp/krb5cc_1001_ywvktf Principal: arodier(a)RED2.SRV Issued Expires Principal Mar 31 09:25:55 Mar 31 19:25:53 krbtgt/RED2.SRV(a)RED2.SRV Mar 31 09:25:57 Mar 31 19:25:53 nfs/ananke.red2.srv(a)RED2.SRV Once I have simply logged myself on a console, I can access my emails using any IMAP client. The question is: How should I configure libpam (or dovecot ?) to initialise/receive a kerberos ticket after successful authentication ? Thanks for your answers.

2 4

[Dovecot] debugging mail_location issues
by Walt Shekrota 31 Mar '11

31 Mar '11

Type of Maildir structure I am using came from KDE. No '.'s just folders. something like Maildir/ INBOX mail-sent outbox other where each has cur new and tmp folders. if I access this directory with IMAP it creates cur new and tmp in the root. ie Maildir/ INBOX cur new tmp mail-sent outbox other This implies to me 1. it finds the Maildir directory 2. it apparently does not have access to the directories like INBOX so it makes its own in the root? or is this a side effect I'm misunderstanding? The resulting IMAP session shows an empty INBOX only (this must be the cur new tmp it added) The real INBOX is not accessible but still intact. In a session this morning I could access all the folders just not the real INBOX. INBOX was as is here empty with cur new tmp in the root of the Maildir folder. This behavior makes no sense. I'm using the hierarchical structure as pointed to in. http://wiki1.dovecot.org/MailLocation/Maildir It appears my grief surrounds dovecot's detection of mailbox. This is kind of what I said days ago. Setting up requires you to know expected states. Something in my environmment I haven't been able to identify (yet) is influencing recognising that hierarchical maildir structure. -Walt

2 1

[Dovecot] WiKi V2
by Jim Knuth 31 Mar '11

31 Mar '11

Hi, small question: Will the WiKi of the version 2 be updated shortly? Many things are not right at all. This would be really very nice. Many thanks in advance. -- Mit freundlichen Grüßen, Jim Knuth P.S.: Bitte senden Sie KEINE HTML-Mails! Zufallszitat: Das Schweigen von gestern rechtfertigt nie das Schweigen von heute. (Otto Schily)

8 11

[Dovecot] Message file prefetching to memory
by Timo Sirainen 31 Mar '11

31 Mar '11

I added a new mail_prefetch_count setting to Dovecot v2.1 (http://hg.dovecot.org/dovecot-2.1/) Its main purpose is to avoid unnecessary latency while waiting for replies from remote server with imapc, i.e. instead of doing (FETCH, wait, FETCH, wait, ...) it can do (FETCH, FETCH, .., wait). For the same reason it's also going to be very useful once I add support for key-value databases / other high latency cloud filesystems. It also works with Maildir, single-dbox and cydir backends by calling posix_fadvise(POSIX_FADV_WILLNEED) for the files. This syscall is apparently only implemented by Linux. It should tell the kernel to start reading the files from disk to page cache. By calling this for multiple files, it should help the kernel optimize disk I/O. For example if 10 files are prefetched, the kernel might figure out that it should read them in a different order to avoid extra disk seeks. Perhaps it also does something useful with NFS, I don't know. I'm not sure if it would be a good idea to use this for mbox or multi-dbox files, since they already have multiple messages in same file so kernel probably already did some prefetching. With mdbox I guess it could be useful if the message file changes.. This optimization currently works only for FETCH command (and POP3 RETR and TOP). SEARCH/THREAD/SORT commands will hopefully implement it soon also. I'd be interested in knowing what the effects of this setting are if anyone tests this some day.

1 0

[Dovecot] Increase /proc/sys/fs/inotify/max_user_instances
by Adrian Stoica 31 Mar '11

31 Mar '11

Hi I allready have set 256 on max_user_instances , and in the log i keep seeing Mar 28 10:08:44 mail dovecot: imap(some.username): Warning: Inotify instance limit for user 98 (UID vmail) exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_instances All users use thunderbird 3.1.9 , and from time to time this show in log , with a random user. What can i do to resolve this issue ? my doveconf-n : # 2.0.11: /usr/dovecot2/etc/dovecot/dovecot.conf # OS: Linux 2.6.35.4 i686 auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 1 mins auth_mechanisms = plain login cram-md5 auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose_passwords = plain base_dir = /var/run/dovecot/ default_client_limit = 5000 default_internal_user = vmail default_login_user = nobody default_process_limit = 200 deliver_log_format = mail from=%f subject=%s msgid=%m: %$ dict { acl = mysql:/usr/dovecot2/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_uid = 1 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_location = maildir:~/Maildir mail_plugins = " quota acl trash 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 namespace { inbox = yes location = prefix = separator = / subscriptions = yes type = private } namespace { hidden = no list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /usr/dovecot2/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = INBOX autosubscribe4 = Sent mail_log_events = delete mailbox_delete mailbox_rename mail_log_group_events = yes quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=95%% quota-warning 90 %u quota_warning3 = storage=85%% quota-warning 85 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve trash = /usr/dovecot2/etc/dovecot/dovecot-trash.conf.ext } postmaster_address = postmaster(a)mydomain.com protocols = imap rejection_subject = Rejected: %s: %r service auth { unix_listener auth-userdb { mode = 0660 user = vmail } } service dict { unix_listener dict { user = vmail } } service imap-login { process_min_avail = 16 service_count = 1 } service imap { process_limit = 2048 vsz_limit = 512 M } service quota-warning { executable = script /bin/quota_warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /usr/dovecot2/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota acl trash notify mail_log sieve autocreate" } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 16 mail_plugins = " quota acl trash notify mail_log imap_quota imap_acl" }

2 2

[Dovecot] log
by Walt Shekrota 30 Mar '11

30 Mar '11

does the following indicate TLS is configured? 2011-03-30 10:37:07 auth(default): Info: client out: OK 1 user=wshek 2011-03-30 10:37:07 auth(default): Info: master in: REQUEST 2 13371 1 2011-03-30 10:37:07 auth(default): Info: passwd(wshek,127.0.0.1): lookup 2011-03-30 10:37:07 auth(default): Info: master out: USER 2 wshek system_groups_user=wshek uid=1000 gid=1000 home=/home/wshek 2011-03-30 10:37:07 imap-login: Info: Login: user=<wshek>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS If it is I do not intend it. How can I turn it off? Thanks. -Walt

2 2

[Dovecot] v1.2.12 and debug
by Walt Shekrota 30 Mar '11

30 Mar '11

Is there some kind of extended debug that might show why my maildir is not foundat login? It has worked off and on, once briefly today then no more. I'm going around twiddling knobs guessing at this point which is foolish. I need some real bread crumbs to indicate what is going wrong. I've tried all kinds of .conf file ... example file etc. I figured using the least number of settings should get me somewhere but I still have no luck. I'd love to just give up and load that PPA for 2.x but I have no idea what package to install in debian. (I have the PPA update) Thanks. -Walt

2 1

[Dovecot] dovecot.conf
by Walt Shekrota 30 Mar '11

30 Mar '11

In 1.2.12 or there abouts how do changes in the dovecot.conf happen? After doing the sig HUP I have noted there is generally a delay in the recognition of items in my .conf. An example I had logging set off, turned it on and it was several restarts before I again saw logging? This delay is driving me nuts in trying to figure out what needs to change. Thanks. -Walt

2 2

[Dovecot] dovecot-lda can not find home dir
by Pete 30 Mar '11

30 Mar '11

Hello, Running dovecot 2.0.11 and pigeonhole on Fedora 14 x86_64. The lda can not seem to find the user's home directory, yet other parts of dovecot (pop3, imap, managesieve) can. Grepping "Effective uid" from /var/log/maillog: Mar 29 11:21:34 new-eagle dovecot: pop3(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:23:18 new-eagle dovecot: imap(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:23:52 new-eagle dovecot: managesieve(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:24:53 new-eagle dovecot: managesieve(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: Effective uid=726, gid=726, home= Although mail does get delivered, the .dovecot.lda-dupes file can not be created because of this: Mar 29 11:26:15 new-eagle dovecot: lda: Debug: Loading modules from directory: /usr/lib64/dovecot Mar 29 11:26:15 new-eagle dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: Effective uid=726, gid=726, home= Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: fs: root=/home/pete/mail, index=, control=, inbox=/var/spool/mail/pete Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: userdb lookup skipped, username taken from passwd lookup for process euid Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: none: root=, index=, control=, inbox= Mar 29 11:26:15 new-eagle dovecot: lda(pete): Error: User pete doesn't have home dir set, disabling duplicate database Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: using sieve path for user's script: /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: opening script /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: script /home/pete/.dovecot.sieve successfully compiled Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: executing script from /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): sieve: msgid=<FF641E3CEA3748B5B7D678ABE85F1A7B@pete1>: stored mail into mailbox 'INBOX' Dovecot seems to be able to determine the user's home directory, but I do not know how to tell dovecot-lda where it is. Running "doveadm user pete" produces: userdb: pete system_groups_user: pete uid : 726 gid : 726 home : /home/pete In /home/pete, the .forward file is: | "/usr/libexec/dovecot/dovecot-lda" Entry from /etc/passwd: pete:x:726:726:Peter:/home/pete:/bin/false Output of dovecot -n: # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35.11-83.fc14.x86_64 x86_64 Fedora release 14 (Laughlin) ext4 auth_cache_size = 10 M auth_debug = yes auth_mechanisms = login plain auth_verbose = yes disable_plaintext_auth = no listen = * mail_debug = yes mail_location = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY 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 mbox_write_locks = fcntl passdb { driver = pam } plugin/sieve = /home/%u/.dovecot.sieve plugin/sieve_dir = /home/%u/sieve protocols = pop3 imap sieve rejection_reason = Sorry, your message was automatically rejected:%n%r rejection_subject = failure notice re: %s service managesieve-login { inet_listener sieve { port = 4190 } } ssl = no userdb { driver = passwd } protocol lda { mail_plugins = sieve I did update from dovecot-2.0.9 (which the lda could find the home directory) but I also had to change the mail_location from: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY to: mail_location = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY Also had to change: plugin/sieve = ~/.dovecot.sieve plugin/sieve_dir = ~/sieve To: plugin/sieve = /home/%u/.dovecot.sieve plugin/sieve_dir = /home/%u/sieve ... in order for 2.0.11 to function. Any thoughts on how to get the home dir passed correctly to lda ? Thanks, Pete

2 3

[Dovecot] service auth { client_limit=4096 } is lower than required under max. load (5720
by Frank Bonnet 30 Mar '11

30 Mar '11

Hello Since I started up dovecot2 this morning I get this kind of warning message when I start Dovecot Help appreciated thanks doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Stopping dovecot. Waiting for PIDS: 79978, 79978. doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Starting dovecot. doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Warning: service auth { client_limit=4096 } is lower than required under max. load (5720)

2 1