- dovecot - dovecot.org

[Dovecot] Public Folder Quotas
by Peter Fraser 28 Oct '09

28 Oct '09

Hi All I'm really busy adding features to dovecot running on my dev box to later move into prod. I saw where public mailbox quotas was added to 1.2 Does anyone have this working? I haven't been able to find docs on that as of yet.

3 2

[Dovecot] Dovecot, Shared Mailboxes (via symlink), and ACLs
by Dave 28 Oct '09

28 Oct '09

Hello! I just joined the list and will be happy to help where I can in my limited experience, but also come to the table with a question. I think there's something I'm missing regarding shared mailboxes and ACLs, so I will describe my situation and see if I am understanding correctly (running Dovecot 1.1.10). I have read over the Dovecot Wiki many times and have scoured many forums but still can't seem to find a solution. I have an IMAP mailbox that is working fine (user imapuser), so the maildir and related structure is in: /home/imapuser/Maildir I have another IMAP mailbox for another imap user, newuser1, also working fine, with maildir and related structure in: /home/newuser1/Maildir I have created a symlink under newuser1's Maildir to imapuser's Maildir so as to give newuser1 access to the things in imapusers's inbox. I have also symlinked inside the newuser1 Maildir to a folder under imapusers's inbox, let's call it "MailingList", basically settiing up something like: /home/newuser1/Maildir: cur/ .imapuserinbox -> /home/imapuser/Maildir .imapusermailinglist -> /home/imapuser/Maildir/MailingList new/ tmp/ (... and various other Dovecot-related files, nothing ACL related.) Now, I have gotten the shared boxes to work IF I changed the permissions to be rwx for user and group on /home/imapuser/Maildir/*, but this makes procmail (and .procmailrc) unhappy and it starts sending things to mbox files (old system) instead of sending them on to the Maildir. So that doesn't seem to work. Which led me to ACLs. Now, I've tried (after enabling the two appropriate lines in dovecot.conf and restarting dovecot, etc) both per-directory ACL files and global ACLs, and while I can get some things to *change* as viewed by my mail client, I can't seem to create consistent behavior. I know that's fairly vague, but it's like I'll change something in the global ACL and folders are affected that I wouldn't anticipate, based on what I'm understanding of ACLs. So, in the example above, if I enable global ACLs, what names do I use to refer to those shared boxes I'm trying to access? Do I use the link name I made, .imapuserinbox or .imapusermailinglist (without leading periods), like /etc/dovecot/acls/imapuserinbox, or is it based off of the original dir name? Like do I need something like /etc/dovecot/acls/MailingList ? What about the "inbox" I'm sharing in /home/imapuser/Maildir, how do I reference that? Is there a way to do it without affecting or changing permissions of other IMAP users and inboxes on the same system? One thing I am receiving consistently in the error logs is: mail dovecot: IMAP(newuser1): stat(/home/newuser1/Maildir/.imapuserinbox/tmp) failed: Permission denied (euid=152(newuser1) egid=100(usergroup) UNIX perms seem ok, ACL problem?) So it seems if I get the ACL stuff right, I will be in business. Any ideas?? Thanks for any help anyone can give!! Dave

3 3

[Dovecot] 1.1 Quota Question
by Marty Anstey 28 Oct '09

28 Oct '09

Hi, I'm not sure if this question has been asked before but some googling hasn't turned up anything really relevant. We are currently running Dovecot 1.1.16 & Postfix; maildir++. When a message arrives for a mailbox which is over quota, it is bounced. Obviously, this isn't very desirable; the primary downside to this is that when junk mail hits a full mailbox it's bounced to that recipient of the message. On a busy mail system, that could potentially get us blacklisted pretty quickly. Ideally we would like to reject the messages inline. Is there an easy way to set this up? Thanks, Marty

2 1

[Dovecot] Error: userdb lookup
by kfx 28 Oct '09

28 Oct '09

Hi list, I am trying to get rid of the "Error: file_dotlock_create(~/.dovecot.lda-dupes) failed: No such file or directory" by adding home directories to my virtual users (ldap). I want this home dir' to be specified like this: /var/vmail/$USER/home/ and the sieve scripts to go to: /var/vmail/$USER/home/sieve/ So as suggested before in this list, I have replaced: user_attrs = mailMessageStore=mail,mailQuotaSize=quota_rule=*:bytes=%$ by user_attrs = mailMessageStore=mail,mailQuotaSize=quota_rule=*:bytes=%$, =home=/var/vmail/%u/home But then the userdb lookup fail and it tells me this in the log: deliver(user@mydomain): Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-master) failed: No such file or directory This is strange because: a. the socket is at /var/run/dovecot/auth-master b. it is working flawlessly with the original user_attrs value So I am thinking that this setting is totally ignored by dovecot at some point. I must be missing something. Any help please ? My postfix's master.cf with the deliver relevant line: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} My postfix's main.cf with the deliver relevant line: mailbox_command = /usr/local/libexec/dovecot/deliver And my dovecot.conf and dovecot-ldap.conf: # 1.2.4: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-164.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot-error.log info_log_path: /var/log/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve ssl_ca_file: /etc/pki/CA/chaine.crt ssl_cert_file: /etc/pki/dovecot/certs/mail.mydomain.pem ssl_key_file: /etc/pki/dovecot/private/mail.mydomain.key login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: Welcome login_processes_count: 8 login_max_processes_count: 192 verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/vmail/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): lda: postmaster_address: postmaster@mydomain hostname: mydomain mail_plugins: quota sieve auth default: username_format: %Ln passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap-userdb.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota quota_rule: *:storage=10GB quota_rule2: Trash:storage=10%% sieve_dir: /var/vmail/%u/home/sieve sieve: /var/sieve-scripts/%u.sieve ############################## dovecot-ldap.conf: uris = ldaps://ldap.mydomain ldaps://ldap2.mydomain tls = no tls_ca_cert_file = /etc/pki/CA/chaine.crt tls_require_cert = never auth_bind = yes auth_bind_userdn = uid=%u,ou=people,dc=mydomain base = ou=people,dc=mydomain user_attrs = mailMessageStore=mail,mailQuotaSize=quota_rule=*:bytes=%$ user_filter = (&(accountStatus=active)(uid=%n)) pass_filter = (&(accountStatus=active)(uid=%u)) ########################################

2 1

[Dovecot] dovecot.log file permissions and ownership
by Jerry 27 Oct '09

27 Oct '09

Using FreeBSD-7.2 and Dovecot v1.2.4 what user does dovecot use to write to its log file? I have the logfile located in the /var/log directory. I have Postfix configured to use 'virtual' users and use dovecot for delivery. While dove can write to the file when accessed for POP services, when accessed via Postfix, I get this error message: Oct 25 07:02:15 scorpio postfix/pipe[56956]: B01BD2287E: to=<user(a)domain.com>, relay=dovecot, delay=220, delays=220/0.01/0/0.04, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/dovecot.log: Permission denied ) I have used the following ownership types for the file: 1) root:wheel 2) dovecot:dovecot 3) root:dovecot 4) dovecot:wheel The only thing that works all the time is to give the file full r/w (0666) permission. That seems extreme. -- Jerry gesbbb(a)yahoo.com |::::======= |::::======= |=========== |=========== | A nuclear war can ruin your whole day.

2 1

[Dovecot] SetUID check problem
by Thomas Berezansky 27 Oct '09

27 Oct '09

Running dovecot 1.2.4 on FreeBSD using Postfix. Everything works fine normally, but deliver is executable by world. This is not normally a problem, as I don't run deliver SetUID root. But for whatever reason, when deliver is called by something that IS SetUID root I get the following error: /usr/local/libexec/dovecot/deliver must not be both world-executable and setuid-root. This allows root exploits. See http://wiki.dovecot.org/LDA#multipleuids Deliver's permissions look like this: -r-xr-xr-x While the program calling deliver has permissions like this: -r-s--x--- If it isn't possible for deliver to differentiate between being called by setuid root programs and being setuid root itself I don't think it should be doing that particular security check. Alternatively, there should be an option to turn that particular check off, but what little I saw of the source code and found searching the documentation told me that there doesn't seem to be such an option already. I also couldn't find any mention that this is fixed by 1.2.5 or 1.2.6. Thomas Berezansky Merrimack Valley Library Consortium

2 1

[Dovecot] Test environment question
by Stewart Dean 27 Oct '09

27 Oct '09

I want to test out my first V1.2 Dovecot (upgraded from V1.1) instance. What I have in mind to do is to run it on another machine that has the Inbox dir and homedirs NFS import mounted from the production mailserver. I then have 5 people test it in this test environment.... A) Then I can deal with the index filesystem in one of two ways: 1) Make it local OR 2) NFS import it from the production DC server Comments as to which is best? I have used #1 before...which caused some temporary unhappiness with the switchover and switchback....during which time the index is badly wrong and DC auto-rebuilds it... B) Is there anything else I should do/not do? C) Any ugliness that will surface in this testing lashup but isn't important? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] Multiple identities
by Koenraad Lelong 27 Oct '09

27 Oct '09

Hi, I recently moved from courier-imap to dovecot, to be able to work with managesieve. I use version 1.2.5, on suse 10.3. I used the script to migrate the courier maildir to dovecot format. It seems to work fine except for one problem : I use a number of aliasses and with Thunderbird I can select which alias (e-mail-address) to use as my identity when sending a mail. I sniffed with wireshark, and with my standard identity, I see the message appended to "Sent", like I expect. If I use an alias, I see a folder being created : "INBOX.Sent", and then the message is appended there. Why the difference ? I'm trying to debug this but dovecot does not help much. I tried rawlog but there is no output (that I see) from it, no log-files in my maildir. Any hints how to proceed ? Output op dovecot -n : # 1.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.22.19-0.4-default x86_64 openSUSE 10.3 (X86-64) base_dir: /var/run/dovecot/ log_path: /var/log/dovecot log_timestamp: %Y-%m-%d %H:%M:%S listen: *:143 ssl_listen: *:993 ssl_ca_file: /etc/postfix/certificate/cacert.org.pem ssl_cert_file: /etc/postfix/certificate/mailbox.pem ssl_key_file: /etc/postfix/certificate/mailboxkey.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 499 last_valid_uid: 499 mail_location: maildir:/var/vmail/%d/%u mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap lda: postmaster_address: postmaster(a)mydomain.com sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/auth-master mail_plugins: cmusieve auth default: mechanisms: plain login user: nobody verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail Kind regards, Koenraad Lelong.

3 6

[Dovecot] Maildir autocreation
by Proskurin Kirill 26 Oct '09

26 Oct '09

Hello. Today i found what maildir autocreation stop work. May be after upgrade to 1.2. Here logs: Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Module loaded: /usr/local/lib/dovecot/lda/lib10_quota_plugin.so Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: auth input: quota_rule=*:storage=2046M Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: auth input: uid=1002 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: auth input: gid=1002 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: auth input: home=/var/spool/dovecot/domains/fxclub.org/shershov-oa Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Home dir not found: /var/spool/dovecot/domains/fxclub.org/shershov-oa Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota root: name= backend=maildir args= Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota rule: root= mailbox=* bytes=2145386496 messages=0 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota rule: root= mailbox=Trash bytes=1317011456 messages=0 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota rule: root= mailbox=SPAM ignored Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota warning: bytes=2038117171 (95%) messages=0 command=/usr/local/bin/quota-warning.sh 95 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: Quota warning: bytes=1716309196 (80%) messages=0 command=/usr/local/bin/quota-warning.sh 80 Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: maildir autodetect: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//cur) failed: No such file or directory Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: mbox autodetect: data=/var/spool/dovecot/domains/fxclub.org/shershov-oa/ Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: mbox autodetect: INBOX file: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa/) failed: No such file or directory Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: mbox autodetect: has .imap/: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//.imap) failed: No such file or directory Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: mbox autodetect: has inbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//inbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Info: mbox autodetect: has mbox: stat(/var/spool/dovecot/domains/fxclub.org/shershov-oa//mbox) failed: No such file or directory Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Error: mail_location: Ambiguous mail location setting, don't know what to do with it: /var/spool/dovecot/domains/fxclub.org/shershov-oa/ (try prefixing it with mbox: or maildir:) Oct 21 11:01:25 deliver(shershov-oa(a)fxclub.org): Fatal: Namespace initialization failed dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmaster(a)fxclub.org hostname: mail.fxclub.org mail_plugins: sieve quota mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ %f %s log_path: /var/log/dovecot/deliver.log info_log_path: /var/log/dovecot/deliver.log sendmail_path: /usr/sbin/sendmail rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam sieve_dir: ~/sieve sieve: ~/.dovecot.sieve sieve_global_path: /var/spool/dovecot/global.sieve mail_location: /var/spool/dovecot/domains/%d/%n/ mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields: uid box msgid size mail_log_max_lines_per_sec: 0 -- Best regards, Proskurin Kirill

5 7

[Dovecot] Multiple postfix + single dovecot - optimal configuration
by Tomek 26 Oct '09

26 Oct '09

Hello, I want to setup dovecot with two postfix servers on three machines: - dovecot - with huge amount of disk space - where all user emails will be kept, - postfix1 - with greylisting, amavisd-new (spamassassin, clamav, etc), with mysql backend, - postfix2 - same as postfix1. MX priority will be set to the same value for both postfix machines. For now I don't know how to "glue" these severs: - if I should install dovecot on both postfix and use third servers as a NFS share? - or maybe it is possible to communicate with dovecot on third server via LMTP? - or should I run third postfix daemon (without antyspam etc - simple configuration) on the same machine as dovecot only for delivering local mails? I will be grateful for any advice, howto or good practices example. -- Regards, Thomas.

3 2

[Dovecot] protocol configure confusion
by Stewart Dean 26 Oct '09

26 Oct '09

The docs say: > > *protocol*s = imap *imaps* > *Protocol*s we want to be serving: imap *imaps* pop3 pop3s If you > only want to use dovecot-auth, you can set this to "none". > and..... > > If you want to specify ports for each service, you will need to > configure these settings inside the *protocol* imap/pop3 { ... } > section, so you can specify different ports for IMAP/POP3. For example: > > # *protocol* imap { > # listen = *:10143 > # ssl_listen = *:10943 > # .. > # } > So if I want to run both imap and imaps AND configure the port, do I do: # *protocol* imap { # listen = *:143 # ssl_listen = *:10943 # } OR # *protocol* imap { # listen = *:143 # } # *protocol* imaps { # listen = *:993 # }

2 1

[Dovecot] Ubuntu stable versions
by Stefan Onken 26 Oct '09

26 Oct '09

Hello, I am using ubuntu-server for some of my servers. Unfortunately the latest version available is 1.1.11. Is there any alternative than building it from source to get the latest dovecot version ? Thanks Stonki

4 9

[Dovecot] Rotating the dovecot log file
by Jerry 24 Oct '09

24 Oct '09

Using FreeBSD-7.2, I am attempting to configure the system newsyslog utility to rotate the dovecot.log file. I would prefer to use the system utility rather than the one described on the dovecot wiki for rotating the file. Unfortunately, it is not working. This is the error message that is spawned: newsyslog: illegal signal number in config file: /var/log/dovecot.log root:wheel 0666 1 * $M1D0 CJ /var/run/dovecot/master.pid USR1 Does anyone have an idea how to get this to work? Thanks! -- Jerry gesbbb(a)yahoo.com |::::======= |::::======= |=========== |=========== | Wilner's Observation: All conversations with a potato should be conducted in private.

2 2

[Dovecot] New error messages
by Robin Atwood 23 Oct '09

23 Oct '09

I was glancing at my logwatch report when I noticed: dovecot: IMAP(robinmail): fchown(/home/robinmail/mail/.imap/INBOX/dovecot.index.log.newlock, -1, 10(wheel)) failed: Operation not permitted (egid=100(users), group based on /var/mail/robinmail): 1 Time(s) dovecot: IMAP(robinmail): fchown(/home/robinmail/mail/.imap/INBOX/dovecot.index.tmp, -1, 10(wheel)) failed: Operation not permitted (egid=100(users), group based on /var/mail/robinmail): 3 Time(s) So what's going on here? :) I am fairly sure I never had them before. Running dovecot 1.2.6. TIA -Robin -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

2 2

[Dovecot] v2.0.alpha2 released
by Timo Sirainen 23 Oct '09

23 Oct '09

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz.sig Changes since alpha1: - All debug messages are now logged to debug log (debug_log_path setting, defaults to info_log_path). Patch by Pascal Volk. - Added support for SORT=DISPLAY IMAP extension. - Added doveadm who command for listing currently logged in users. - ssl_ciphers_list: Disable anonymous and export ciphers by default. - mail_chroot can now contain %variables (e.g. /home/%u) - fixed a bad maildir crashing bug - ssl-params is now run with +15 priority when generating the ssl parameters - Redesigned how login processes log in and create imap/pop3 processes. This fixes several settings and some other problems, plus it's now also possible for a single imap/pop3 process to handle multiple connections. If you want to try this, modify master.conf: service imap { # comment out: #service_count = 1 # This should be at least the number of CPUs, maybe more (2-3x?) process_min_avail = 4 # Limit the number of clients a single process can handle. # Disk IO is blocking, so some commands can take a while. client_limit = 5 } It currently doesn't even try to group same user's connections to same process, they'll just go randomly to whichever process manages to accept it first. Some day perhaps there should be a new service in the middle that keeps track of existing connections and forwards new ones to right mail processes. v2.0.beta1 TODO list: - master.conf has to be somehow put into defaults, so doveconf -n doesn't show its contents. an example master.conf would be minimal and show only those settings that admin might want to change (and those would show up in doveconf -n) - verbose_proctitle=yes is now quite useless because of the imap/pop3 process creation change. Probably enable linux-proctitle-hack and start changing the proctitle much more often. For example it could contain the command that's currently being run by user. And login processes could contain how many client connections they currently have. And other processes too something similar.. - change plugin hook design to allow multiple users in same process to run different plugins See alpha1 release announcement for more about these TODO: - v1.x config backwards compatibility - dsync is buggy - config process is slow - tcp-wrappers support

4 4

[Dovecot] Capability info in hello message not complete?
by Michal Hlavinka 23 Oct '09

23 Oct '09

Hi, one Fedora user complains about not some troubles after update to dovecot 1.2. He suspects wrong capability information given by dovecot 1.2 In dovecot.conf he uses imap_capability= option. While response to 'A CAPABILITY' respects imap_capability value, the capability info in hello message does not. for imap_capability=IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN A CAPABILITY response is: * CAPABILITY IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN but hello message is: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. But it seems even when imap_capability is not used capability in hello message is not complete: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. vs. * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH STARTTLS AUTH=PLAIN is this expected? Do you think capability information in hello message really can befool clients? Regards, Michal Hlavinka

2 7

[Dovecot] HA Dovecot Config?
by dovecot＠corwyn.net 23 Oct '09

23 Oct '09

Hi! I'm currently running Dovecot 1.1.8 on a HP server using CentOS 5.2 as my IMAP server, receiving mail from postfix, and also using squirrelmail as the frontend. As I look at upgrading the mail server, I'd like to change to a higher availability configuration (where the server can fail and I don't have to reconfig my imap users). For the SMTP that's easy, because I can use multiple MX records, and I can redirect a port forward from one server to another. But IMAP doesn't have the same functionality, because it's the storage that matters. What's the "best" way to do that? Clustered servers using a SAN? NAS? some sort of appliance in front? Suggestions? Thanks! Rick Rick Steeves http://www.sinister.net In reality nothing is more damaging to the adventurous spirit within a man than a secure future - Alexander Supertramp

11 16

[Dovecot] doveadm who
by Timo Sirainen 23 Oct '09

23 Oct '09

Pascal Volk suggested this, and it was pretty quick to implement for Dovecot v2.0. Ideas welcome how to improve it, or if it's already perfect :) The first line is written to stderr, so |sort can be used: # doveadm who|sort username # (ips) (pids) timo 1 (127.0.0.1) (2457) tss 2 (127.0.0.1) (617 1345) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) # doveadm who|sort -k2 -nr username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345) timo 1 (127.0.0.1) (2457) You can filter connections: # doveadm who 127.0.0.2 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) # doveadm who 127.0.0.0/24 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) timo 1 (127.0.0.1) (2457) tss 2 (127.0.0.1) (617 1345) # doveadm who tss username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345) # doveadm who tss 127.0.0.1 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345)

1 0

[Dovecot] Need a little shadow to MySQL conversion help
by Marc Perkel 22 Oct '09

22 Oct '09

Excuse me for being stupid and confused. I'm trying to convert my dovecot install from passwd-file to mysql. I have a single table called "users" that has 3 fields, user_name, domain_name and password. The data came from passwd/shadow files so it uses the same password encryption as the shadow files do. The directory where the email is stored is calculated elsewhere and not stored in the database. The UID and GID are both mail for all virtual users. The user logs in passing the full email address and the password. So - what would be the config for using MySQL? Do I even need a userdb? If so - what would it be? Thanks in advance.

4 11

[Dovecot] VZW Blackberry BIS problems?
by B. Cook 22 Oct '09

22 Oct '09

Ever since Columbus day things have been strange with my two dovecot servers, according to my Blackberry users. We do not have a BES just the standard BIS that comes with a personal account. Several people have told me that since that Monday that they get occasional duplicate copies of messages which only appear singularly in their Maildir inboxes. I myself even called VZW and got transferred to RIM themselves where they 'reset' my account; (same as me going into the BIS server and deleting and adding again) only to have the same thing happen; again occasionally.. Below is relevant dovecot info.. -r-xr-xr-x 1 root wheel 164064 Oct 1 17:16 /usr/local/sbin/dovecot (date it was built; prior to any problems.. *whew*) ;) 1 # 1.2.4: /usr/local/etc/dovecot.conf 2 # OS: FreeBSD 7.2-RELEASE-p3 i386 3 ssl_cert_file: /usr/local/etc/lighttpd/ssl/mail.poughkeepsieschools.org.pem 4 ssl_key_file: /usr/local/etc/lighttpd/ssl/mail.poughkeepsieschools.org.pem 5 disable_plaintext_auth: no 6 verbose_ssl: yes 7 login_dir: /var/run/dovecot/login 8 login_executable: /usr/local/libexec/dovecot/imap-login 9 login_greeting: mail.poughkeepsieschools.org OK 10 first_valid_uid: 89 11 last_valid_uid: 89 12 first_valid_gid: 89 13 last_valid_gid: 89 14 maildir_copy_preserve_filename: yes 15 mail_plugins: quota imap_quota 16 imap_client_workarounds: delay-newmail outlook-idle tb-extra-mailbox-sep 17 auth default: 18 mechanisms: plain login 19 user: vpopmail 20 passdb: 21 driver: vpopmail 22 userdb: 23 driver: vpopmail 24 socket: 25 type: listen 26 client: 27 path: /var/run/dovecot/auth-client 28 mode: 438 29 plugin: 30 quota: maildir:User quota 31 expire: Trash 7 Spam 30 Now what does not show here is something that I put in that it looked like it was supposed to help but didn't.. mailbox_idle_check_interval = 30 after looking around at other people complaining about BIS and possible dovecot issues it seemed that that entry was the 'magic' the BIS was missing; except I never had it and never had troubles. I'm assuming this is a BIS issue of some sort, but I can't tell. After looking on the wiki I didn't see anything that says "BIS users look here for tips.. " So I'm assuming there aren't any; I think it should just work with the IMAP server.. Any help would be appreciated as everyone thinks this is 'our problem' and "if we had an exchange server we wouldn't be having these problems.." Thanks in advance..

3 3

[Dovecot] sieve + redirect + as attachment
by Jerry 22 Oct '09

22 Oct '09

Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? -- Jerry gesbbb(a)yahoo.com |::::======= |::::======= |=========== |=========== | A woman was in love with fourteen soldiers, it was clearly platoonic.

3 6

[Dovecot] Public Folders
by Peter Fraser 22 Oct '09

22 Oct '09

Hi All I'm trying to implement public folders. My dovecot -n readout is at the bottom. I created a maildir called resumes in /home/public Its contents are: mail# ls -la /home/public/resumes total 6 drwx------ 3 vmail vmail 512 Oct 22 08:58 . drwx------ 4 vmail vmail 512 Oct 22 08:47 .. drwx------ 5 vmail vmail 512 Oct 22 08:58 Maildir -rw------- 1 vmail vmail 0 Oct 21 18:30 dovecot-acl-list Then I created a directory called resumes in /usr/local/etc/dovecot-acls and in it, I created the file dovecot-acl I put the following entries in dovecot-acl owner lrwstiekxa user=user1 rwl When I connect as user1 in thunderbird, right click on the inbox and go subscribe, I see a greyed out public which I cannot subscribe to. I do not see resumes. Any ideas on why this is? mail# dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p1 i386 protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/etc/dovecot/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/dovecot/ssl/private/dovecot.pem ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Mail Server ready. verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: vmail mail_location: maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/tmp/index mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota acl imap_acl mail_plugins(imap): quota imap_quota acl imap_acl mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh dict_db_config: /usr/local/etc/dovecot-db.conf namespace: type: public separator: / prefix: public/ location: maildir:/home/public list: yes subscriptions: yes namespace: type: private separator: / location: maildir:/home/vmail/%u/Maildir inbox: yes list: yes subscriptions: yes lda: mail_plugins: quota acl postmaster_address: postmaster(a)example.com sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login username_format: %Lu debug: yes passdb: driver: pam args: session=yes dovecot passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/vmail/%u allow_all_users=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota2: maildir:user quota quota_rule: *:storage=512M quota_rule2: Trash:storage=10M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/etc/dovecot/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/etc/dovecot/quota-warning.sh 80 acl: vfile:/usr/local/etc/dovecot-acls:cache_secs=300

2 1

Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
by Brandon Davidson 22 Oct '09

22 Oct '09

Hi Marco, On 10/22/09 1:50 AM, "Marco Nenciarini" <mnencia(a)prato.linux.it> wrote: > This morning it happened another time, another time during the daily > cron execution. > > Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev > 0.12 inode 1005 > Oct 22 06:26:57 server dovecot: dovecot: Temporary failure in creating > login processes, slowing down for now > Oct 22 06:26:57 server dovecot: dovecot: child 21311 (login) killed with > signal 6 (core dumps disabled) > > I have dovecot 1.2.6 with Timo's patch to check leaked descriptors. I rebuilt the binaries on our hosts with optimization disabled, and I'm still waiting for it to reoccur so I can gather file descriptor information and a core. I don't have the leak-detect patch applied. Let's see what Timo has to say about that log file bit. Since it seems to happen to you fairly frequently, it might be worth enabling core dumps as well? -Brad

2 1

[Dovecot] NFS random redirects
by Thomas Hummel 22 Oct '09

22 Oct '09

Hello, Dovecot documentation states that the "random redirects to multiple servers" NFS solution is to be avoided and I'm investigation the actual risks of it and a way to put it to test. I'm running dovecot-1.2.6 with Maildir (indexes, mailboxes and control files are all on NFS) and I'm using procmail instead of deliver as the LDA. 1. Documentation says : "Dovecot locks the maildir while doing modifications to it or while looking for new messages in it" and then mention the "dovecot-uidlist.lock" dotlock file. a) if that file fcntl'ed in addition (i.e. dotlocked + fcntled or just dotlocked) ? b) is that file THE way to lock the Maildir mentionned above or is it just something else used only for updating that particular file (i.e. is Maildir locked in some way + dovecot-uidlist.lock created or just dovecot-uidlist.lock created) ? 2. Documentation says : "NFS caching is a big problem when multiple computers are accessing the same mailbox simultaneously" I guess it's because of the dotlocks files and not fcntl locking ? Is there anything else than dovecot-uidlist which is dotlocked ? If yes, is it dotlocked only or dotlocked and fcntled ? 3. Documentation says : "Dovecot v1.1 flushes NFS caches when needed if you set mail_nfs_storage=yes" How can a program flush the NFS caches ? By which (system) call ? 4. Documentation says : "Besides the NFS cache problems described above, mailbox contents can't be cached as well in the memory either." Is it about in-memory indexes or part of indexes loaded into memory ? 5. How can I torture-test concurrent access to the same mailbox through 2 dovecot servers ? I don't see imaptest.c anymore on http://dovecot.org/tools but I see 2 nfs_test ? Is there some command line options I should use ? 6. when and why can a random redirect to multiple server can cause mailbox corruption ? On flags only or on content as well ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

4 9

[Dovecot] deliver+sieve: Destination address (-a) parsing changes
by Frank Behrens 21 Oct '09

21 Oct '09

When I upgraded my old, long running dovecot 1.1 to newer dovecot-1.2.4 + doevecot-sieve- 0.1.12 I observed a change in destination address (-a) parsing. Old behaviour: When Timo introduced this feature (http://www.dovecot.org/list/dovecot/2007-September/025813.html) it was possible to hand over only the detail part. In my sendmail configuration I used "-a +$h", where $h contains the detail part and may be empty. By default sendmail can call the delivery agent with the following information: $u: The recipient user (always set) $h: Detail part, may be empty $g: The sender address (relative to the recipient). New behaviour: The current sieve version needs a complete address with local- and domain-part. Otherwise we get a warning like deliver(user): sieve: envelope recipient address 'user' is unparseable. The problem is, that the domain part is not always available, e.g. for local delivered emails. This is the main problem, although the setup could be simplified if deliver would accept the old syntax. I'm going to make modifications to sendmail to be able to have all address information available, but this will not solve the problem with missing domain. Now comes my question: Is it better to enhance the address parsing in sieve plugin or should I use a wrapper around deliver? The latter is not very difficult, but introduces an additional process (that may fail). Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.

3 7