- dovecot - dovecot.org

[Dovecot] sieve and fileinto encoding
by proton-sss 28 Oct '09

28 Oct '09

Hello All! I`m using dovecot 1.2.6 I have folder named in russian "САПП", and when in filter i wrote: fileinto "САПП"; all works well. Now i find 2 web applications to manage sieve filters (horde-ingo and squirrelmail/avelsieve) - then creates filter like this: if header :contains "Subject" "САПП" { fileinto "&BCEEEAQfBB8-"; stop; } And creates another folder ".&-BCEEEAQfBB8-", but GOOD folder name already exist ".&BCEEEAQfBB8-". Please help to understand why dovecots deliver make this happen. Best regards Michael p.s. dovecot -n # 1.2.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-hardened-r9 i686 Gentoo Base System release 1.12.11.1 reiserfs log_path: /var/log/dovecot_err.log info_log_path: /var/log/dovecot_info.log protocols: imap pop3 imaps pop3s managesieve ssl_cert_file: /etc/dovecot/ssl/mail.proton-sss.ru.pem ssl_key_file: /etc/dovecot/ssl/mail.proton-sss.ru.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_location: maildir:/home/%u/.maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): acl imap_acl mail_plugins(imap): acl imap_acl mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%u/ location: maildir:%%h/.maildir/:INDEX=%h/.maildir/shared/%%u list: children subscriptions: yes lda: postmaster_address: postmaster(a)example.com mail_plugins: acl sieve mail_plugin_dir: /usr/lib/dovecot/lda log_path: /var/log/dovecot_deliver.log auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: mail group: users plugin: acl: vfile acl_shared_dict: file:/var/lib/dovecot/shared-mailboxes sieve: %h/.dovecot.sieve sieve_dir: %h/sieve dict: expire: db:/var/lib/dovecot/expire.db

4 7

[Dovecot] antispam-plugin 1.2 and trailing carriage-returns
by Karsten Bräckelmann 28 Oct '09

28 Oct '09

Guys, Dovecot 1.0.15 [1], just built the latest antispam-plugin 1.2 (tarball) for testing, mailtrain backend for SA integration. Both built from custom spec files. The mail that is being trained is different than its respective source in the mbox file. The trained one shows added, trailing carriage-return chars for all headers, which are not in the headers in the mbox file. This breaks sa-learn -- both these variations are different, and SA would learn *both* when run against each one separately. How comes? Any insight? How could I fix this, other than wrapping the sa-learn inside another shell script and have sed strip off the noise? This becomes more of an issue, once I switch from sa-learn to the lightning-fast spamc training variant. TIA guenther [1] Yes, I know, sorry. Don't want to change everything at the same time, and the target system I'm experimenting for runs that version, too. -- char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

3 5

[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