- dovecot - dovecot.org

[Dovecot] Upgrade Dovecot 1.2.7 to 1.2.8 on OS X (10.6.2)
by Tom Kardos 23 Nov '09

23 Nov '09

Hi there, I've tried to update Dovecot to the latest version and have come upon an error during make. Previous upgrades have all been very easy (thank you!) and it appears that the updated make script includes a wget command and unfortunately OS X does not come with wget by default (curl is the default). Not being completely up to speed with the whole autoconf and make process, I'm a little at a loss as to where to even look for making a modification to use curl instead of wget - any assistance would be appreciated. Thanks in advance Tom

4 7

[Dovecot] quota in SQL and static userdb
by Lampa 23 Nov '09

23 Nov '09

Hello, which solution will be working or will be working better (performance). Using dovecot 1.2.6 (plugin section contains quota_rule = *:storage=500M:messages=10000 and i need override this default quota for some users) A) passdb sql(SELECT userid AS user, pw AS password, quota AS userdb_quota_rule FROM users WHERE userid = '%u') + userdb static (uid=500 gid=500 home=/home/mail/%d/%n allow_all_users=yes) - using extra fields quota with no prefetch userdb or B) passdb sql(SELECT userid AS user, pw AS password, quota AS userdb_quota_rule, CONCAT('/home/mail/', domain, '/', user) AS userdb_home, 500 AS userdb_uid, 500 AS userdb_gid FROM users WHERE userid = '%u') + prefetch (eg same sql file) Solution for LDA only(postfix local delivery) and for another IMAP/POP3 dovecot instance? And how to implement domain quotas (something like user quotas using dict) ? Thank you. -- Lampa

3 2

[Dovecot] How to remove leading dots from folder names with Layout=FS
by Tony Rutherford 23 Nov '09

23 Nov '09

We are looking to move to Dovecot from a customized Courier implementation. Our current format is maildir-like. It's basically a filesystem layout...hierarchies are identified by real directories/subdirectories. Our folder names do have a leading dot and for reasons related to other systems, we do not want to change our format at all.The Layout=FS is very close to working for us. The problem we have is the folder names are coming back with the leading dot to the clients. Is there a way through configuration to have the leading dot removed?So, just to clarify, under our maildir home, we have directories (folders) for example: .Trash, .Sent-Mail, etc. Then, any child folders would be resident in the physical subdirectories. Like I said, things appear to work ok, except our List is coming back with .Trash, .Sent-Mail, etc....we would like simply Trash, Sent-Mail, etc.Thanks,...Tony This message is intended solely for the individual(s) to whom it is addressed. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you believe you received this message in error, please notify the sender and delete from your system. Thank you.

2 1

[Dovecot] trivial documentation errata (1.2.7)
by Frank Cusack 23 Nov '09

23 Nov '09

The default dovecot.conf says # Dictionary can be used by some plugins to store key=value lists. # Currently this is only used by dict quota backend. Looks like expire uses dict as well. The managesieve comments are stale as well, with a reference to sieve_storage still in there. Or do they refer to the CMU sieve implementation? Anyway it is confusing. -frank

3 2

[Dovecot] [OT] preferred clients
by Jonathan 23 Nov '09

23 Nov '09

I'm getting tired of Thunderbird telling me I have unread messages in folders that haven't gotten new messages for months so I'm looking for a new mail client. I know the problem lies with Thunderbird because everything is fine via RoundCube and if it tell Thunderbird to rebuild it's index it shows the folder correctly again. Except of course for a subset of the messages in my inbox that it insists where delivered at the exact time I re-indexed it, every time. So what IMAP clients do people prefer these days? Preferably windows or cross platform and it needs to have decent key bindings because (probably like many of you) I get 100s of emails a day via lists and anything that speeds my way through them is good. I run my own server (probably obvious being on this list) and can install webmail clients as well. I ran squirrelmail for a while but although functional it's quite dated. I'm using RoundCube for access away from my systems now but it lacks keyboard shortcut support and trying to click one email after another with a laptop touchpad gets painful fast. Thanks, Jonathan

19 53

[Dovecot] Override Quota with post-login scripting problem
by Yorck Koehler 23 Nov '09

23 Nov '09

Hi everyone, I do have the following dovecot-setup: Passdb: PAM (Winbind-auth and pam_mkhomedir-session) Userdb: passwd (NSS-winbind) This validates/creates my users with aid of my running ActiveDirectory. Now the problem: My global quota policy works fine, but I need to override them for some users. I was sucessful within IMAP itself. I use post-login scripting for that. The mail-clients displays the user-quota correctly. But delivery is still a problem, because I'm unable to override the settings there with post-login scripting. Everytime I send messages to such a user, dovecot sends it back with "Quota exceeded (mailbox for user is full)"... My Question: Is it possible to override the lda quota like I can do it within imap ? (I dont want to change my setup to MYSQL DB only for per-user Quota, if its possible to use a simple file with names and quota) This is the post-login script: #quotaperuser.sh #!/bin/sh case "$USER" in "ZAGH-V+username") QUOTA_RULE='*:storage=500M';; "ZAGH-V+test") QUOTA_RULE='*:storage=5000M';; esac exec /usr/local/libexec/dovecot/imap $* My Configuration: {dovecot -n} # 1.2.3: /usr/local/etc/dovecot.conf # OS: Linux 2.6.16.60-0.54.5-smp i686 SUSE Linux Enterprise Server 10 (i586) base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.err info_log_path: /var/log/dovecot.info protocols: imap imaps pop3 ssl_listen: * 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 mail_location: maildir:~/Maildir mail_full_filesystem_access: yes mail_executable(default): /usr/local/bin/quotaperuser.sh mail_executable(imap): /usr/local/bin/quotaperuser.sh mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota expire mail_plugins(imap): quota imap_quota expire mail_plugins(pop3): quota expire 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 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %v.%u lda: postmaster_address: postmaster(a)zag.de mail_plugins: sieve quota expire mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: no deliver_log_format: msgid=%m subject=%s from=%f status=%$ auth default: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@+ username_format: zagh-v+%u failure_delay: 0 passdb: driver: pam args: session=yes dovecot userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve quota: maildir:Quota quota_rule: *:storage=100M quota_rule2: Trash:storage=100M quota_warning: storage=90%% /usr/local/bin/quota-warning.sh 90 quota_warning2: storage=75%% /usr/local/bin/quota-warning.sh 75 expire: trash 7 expire_dict: proxy::expire

2 3

[Dovecot] v1.2.8 released
by Timo Sirainen 23 Nov '09

23 Nov '09

http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz.sig This is mainly to fix the 0777 base_dir creation issue, which could be considered a security hole, exploitable by local users. An attacker could for example replace Dovecot's auth socket and log in as other users. Gaining root privileges isn't possible though. This affects only v1.2 users, v1.1 and older versions were creating the directory with 0755 permission. If your Dovecot's base_dir isn't in /var/run/dovecot/, you should also make sure that the $prefix/var/ and $prefix/var/run/ (i.e. /usr/local/var/, /usr/local/var/run/ by default) aren't 0777. * Dovecot v1.2.x had been creating base_dir (and its parents if necessary) with 0777 permissions. The base_dir's permissions get changed to 0755 automatically at startup, but you may need to chmod the parent directories manually. - acl: If user has rights from more than one group, merge them instead of choosing one group's rights and ignoring others. - virtual: When using a lot of mailboxes, the virtual mailbox's header could have grown over 32 kB and caused "out of memory" crashes. Also over 64 kB headers couldn't even be updated with existing transaction log records. Added a new record type that gets used with >=64 kB headers. Older Dovecot versions don't understand this header and will log errors if they see it. - FETCH BODYSTRUCTURE didn't return RFC 2231 "key*" fields correctly

4 6

[Dovecot] migrating from Courier
by LuKreme 23 Nov '09

23 Nov '09

I've been running postfix/courier-ssl/MySQL/postfixadmin for years, but since I am in the process of building a new server I decide to reexamine my options. I'm sticking with postfix, but I've decided to move from courier to dovecot because everyone is telling me it's much faster, and I really dislike courier's SASL setup and integration with other services. Of course, I have dozens (but not hundreds) of gigabytes of Courier Maildirs for all the users. Most of the users are in MySQL virtual domains and their mail is stored in a common directory (/usr/local/virtual) and owned by a single system user (vpopmail). I've even hacked together a postfix service to run procmail for the virtual users, though my intention of creating a webface allowing them to muck up their own .procmailrcs never came to fruition. I'm doing my user migration in two steps. First, I will rsync all the mail (and all the user webfiles) to the new server, do any setup/conversion/&c to the data on the new server and make sure everything is working and that passwords are preserved. Then, right before the server goes live I will shutdown mail on the old machine, rsync any new mail (hopefully no more than a couple of hours worth) over, do any conversion, and then fire up the new server. 1) what do I need to do to convert or prepare the courier maildirs for dovecot? 2) is the current setup of virtual users reasonable for dovecot? 2.1) Is there a better option than postfixadmin? 3) some of my users are not in MySQL, but are real system users. Is this going to confuse dovecot (it confuses courier no end). These system users are still using courier and courier maildirs. 4) would it be better to take the server live and THEN move/convert the old mail? 5) anything else obvious that I didn't mention or ask that I should have? The most important thing, of course, is to not lose anyone's email. -- "Two years from now, spam will be solved," -- Bill Gates, January, 2004

4 3

[Dovecot] Dovecot and SATA Backend
by Nicolas GRENECHE 23 Nov '09

23 Nov '09

Hi all, I plan to run a dovecot IMAPS and POPS service on our network. We handle about 3 000 mailboxes. I thought first buying a topnotch server (8 cores and 16 Go RAM) with equalogic iSCSI SAN SAS 15K for storage backend. On second though (and after a comprhensive read of dovecot features), I saw in http://wiki.dovecot.org/MailLocation that index files can be created on a separete local filesystem. My question is : for 3000 users, is it possible to have only a SATA backend attached to my topnotch server (to handle bigger mail quotas) by storing index on local hard drives (SAS drives) ? Extra question, what is the better : iSCSI SATA backend or NFS share ? NFS share is more convenient to have a failover server. Thanks for your help. Regards, -- Nicolas Grenèche - Orléans University - France http://blog.garnett.fr (in french)

8 13

Re: [Dovecot] Sieve plugin: Filtering UTF-8 Emails
by micha＠pocomail.de 23 Nov '09

23 Nov '09

Am Montag, den 23.11.2009 0:53:15 schrieb Pascal Volk <user+dovecot(a)localhost.localdomain.org>... > Please stop top posting. > > Your installation is horrible old. You may consider an update. > > You are using the omparator "i;ascii-casemap". Please read in RFC 2244 > section 3.4 about it <http://tools.ietf.org/html/rfc2244#section-3.4>. > And you will know, why your rule never will match. > You could test my working script from my last message. > > > Regards, > Pascal okay, thank you !!!!!!! michael

1 0