May 2009 - dovecot - dovecot.org

[Dovecot] Dovecot / Sieve
by Joan 02 Jul '09

02 Jul '09

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, Joan

3 10

[Dovecot] Users with large (4GB) inboxes crippling dovecot
by robforrest 30 Jun '09

30 Jun '09

Hi all, I'm new here and would very much appreciate any help you can give me. We are running a rather outdated mail server that until recently has been running beautifully. Under the pretense of "it is ain't broke, don't fix it" it hasn't been updated so is running Fedora Core 4 and dovecot v0.99.14. What is happening is that as users log in (via thunderbird), they are shown the contents of their mailboxes. However, when they try and access a given email, they get no response even if they wait upwards of 10 minutes. I believe that the problem has arisen from their huge inboxes, several users have inboxes in excess of 4GB. Do any of you know how I could split these large mbox files down in to manageable chunks of 1GB? Please be aware that I only have remote access to the server over a modest internet connection. Thanks again for any suggestions. Rob -- View this message in context: http://www.nabble.com/Users-with-large-%284GB%29-inboxes-crippling-dovecot-… Sent from the Dovecot mailing list archive at Nabble.com.

16 28

[Dovecot] Spliting Folders for Efficiency
by Daniel Watts 28 Jun '09

28 Jun '09

Dear Timo, Would there be any sense in giving Dovecot the option to split folders into multiple subfolders when they reached a specified size (probably message count) limit? Dovecot would monitor folders and when they reached, say, 10,000 messages, silently split the folder on the filesystem to ensure that access remains fast. I know that Dovecot scales very well but this would give practically unlimited storage capability and also keep things fast. You could even have it so that the latest 100 messages are kept in their own folder for fast access. .Folder.new .Folder.cur .Folder.tmp could become: .Folder__1.new .Folder__1.cur .Folder__1.tmp and .Folder__2.new .Folder__2.cur .Folder__2.tmp with Dovecot merging them before display as just "Folder" within the mail client. This could be further extended so that Dovecot could be configured to store 'old' message folders in a separate location. We could then have slower+cheaper+larger storage mounted so that 'old mail' does not take up the expensive local SCSI disks on the machine. Mail from 2 years ago is much less likely to be accessed than mail from the last week. This would provide very neat behind-the-scenes archiving functionality. Looking forward to hearing your thoughts. Best, Daniel -- Squirrelmail Stable 1.4.8 (and developing on 1.5.2) PHP 5.x Hardened with Eaccelerator Apache 2.x Mysql 5.0.x Imapproxy over Dovecot 1.0.rc27 with Maildir all running on Gentoo Linux for ~5,000 users.

7 11

Re: [Dovecot] How do I get my mail from fetchmail into dovecot
by Michael Steinbeck-Reeves 22 Jun '09

22 Jun '09

> Message: 3 > Date: Wed, 29 Apr 2009 16:53:49 +0300 > From: Odhiambo ????? <odhiambo(a)gmail.com> > Subject: Re: [Dovecot] How do I get my mail from fetchmail into > dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: > <991123400904290653g205c603m2e4b511486a69b52(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Wed, Apr 29, 2009 at 4:46 PM, Michael Steinbeck-Reeves < > michael(a)steinbeck-reeves.uk.com> wrote: > > > I have dovecot (with squirrel mail etc.) running without any problems > > but cannot understand how to get e-mail from a pop server into dovecot. > > I have fetchmail configured to pick up the mail from the pop3 server but > > don't understand how to get it from there into my dovecot mbox > > > Where does fetchmail put the e-mails? > Point dovecot there with "mail_location =..." then use your favorite MuA to > access the e-mail. That is the problem, fetchmail just forwards it to port 25 (I think) and I need to work out what to put between fetchmail and dovecot in order to get the mail into the correct folders... And I am just going around in circles on this at the moment. Any hint would be appreciated! Thanks, Michael

6 6

[Dovecot] compressed mbox patch
by Axel Thimm 16 Jun '09

16 Jun '09

Some ages ago there existed a compressed mbox patch, but now all I can find are posting about it. Does such a beast exist and would it remotely apply to today's dovecot? If not, is there any hope that something like that emerges? Thanks! -- Axel.Thimm at ATrpms.net

3 5

[Dovecot] Authentication cache, failure to login after changed password
by Tom Sommer 16 Jun '09

16 Jun '09

Hi, I have an issue with the authentication cache. When a user changes his password, the cache doesn't seem to get flushed. Meaning the user is unable to log in to his IMAP account after changing his password. Flow: - Log into IMAP account using pass1 - Approved - Stored in auth cache - Change password to pass2 in MySQL - Log into IMAP account using pass2 - Access is denied - Restart dovecot - Log into IMAP account using pass2 - Approved I'd really like to continue to use the auth cache, is there any solution to the above? perhaps a way to debug the cache and auth process? I wasn't able to activate auth_debug without restarting Dovecot and solving the problem. Using version 1.1.1, MySQL userdb, with "nopassword=Y". Maybe it's due to nopassword? Thanks -- Tom

2 16

[Dovecot] Some questions about deliver
by Axel Luttgens 04 Jun '09

04 Jun '09

While investigating Dovecot's deliver with Postfix, I encountered some behaviors making me wonder whether I really understand the purpose of that binary. So, if you allow... This is from Postfix' main.cf: mailbox_command = /usr/local/dovecot/libexec/dovecot/deliver -e -n This is my quick setup for Dovecot: # 1.2.rc4: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/dovecot-1.2.rc4/libexec/dovecot/pop3- login first_valid_uid: 2001 mail_location: mbox:~/_mailboxes:INBOX=~/_inbox/mailspool mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable: /usr/local/dovecot-1.2.rc4/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/dovecot-1.2.rc4/lib/dovecot/pop3 pop3_lock_session: yes pop3_uidl_format: %08Xv%08Xu auth default: passdb: driver: pam args: * userdb: driver: passwd Here is an excerpt from mail.log: postfix/smtpd[4117]: connect from localhost[127.0.0.1] postfix/smtpd[4117]: 163E1CA2675: client=localhost[127.0.0.1] postfix/cleanup[4120]: 163E1CA2675: message-id=<27002A3F-AF44-410D-A500-368D04F5FA9A(a)almbp.local > postfix/qmgr[3232]: 163E1CA2675: from=<testuser(a)almbp.local>, size=2650, nrcpt=1 (queue active) dovecot[4129]: deliver(www): mail_location: mbox: mkdir(/Library/ WebServer/_mailboxes) failed: Permission denied (euid=70(_www) egid=70(_www) missing +w perm: /Library/WebServer) dovecot[4129]: deliver(www): Fatal: Namespace initialization failed postfix/local[4122]: 163E1CA2675: to=<www(a)almbp.local>, relay=local, delay=0.09, delays=0.02/0/0/0.07, dsn=4.3.0, status=deferred (temporary failure) postfix/smtpd[4117]: disconnect from localhost[127.0.0.1] 1. Shouldn't deliver honor the first_valid_uid setting? After all, if some user isn't allowed to login, is that user supposed to receive mail? 2. What exactly is the -e option supposed to do? User _www clearly isn't configured for receiving mail, but Postfix will nevertheless try to deliver the message until maximal_queue_lifetime has expired. From the log excerpt, it appears that Postfix has been led to consider a temporary failure; unless I'm wrong, that's because Postfix didn't receive neither a "D.S.N text" string nor an EX_* fatal return code. From deliver.c, it seems that many calls to i_fatal() are liable to be executed before the -e option is taken into account (through the local variable stderr_rejection). As a result, I'm wondering under which circumstances exactly deliver is liable to return EX_NOPERM, so that Postfix may consider a permanent failure and bounce the message. Note that the question may somehow be re-phrased as: when invoked without the -e option, under which circumstances will deliver send a rejection message? 3. Doesn't failure_exit_callback() in deliver.c tend to merge many (possibly dissimilar) errors into the single EX_TEMPFAIL one? And BTW, is that function guaranteed to be always called with an EX_* value? Seems to be the case, but... ;-) TIA for your patience, Axel

2 5

[Dovecot] Maildir compression utility
by John Fawcett 04 Jun '09

04 Jun '09

Does anyone know of a script to compress old mails stored in a maildir format by carrying out the steps described at http://wiki.dovecot.org/Plugins/Zlib thanks, John

2 2

[Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
by e-frog 03 Jun '09

03 Jun '09

Hi Timo, Trying 1.2.beta1 with expire plugin currently: When I set mail_location = maildir:~/.maildir the expire plugin doesn't delete messages. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: no messages left I also noticed that above command creates a new but empty directory 'mail' in user's home dir. However using mail_location = maildir:~/Maildir and of course moving the messages to it works. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: seq=1 uid=4078: Expunge . . Info: foo/Trash: seq=100 uid=4178: Expunge Info: foo/Trash: seq=101 uid=4179: Expunge Info: foo/Trash: timestamp 1235292536 -> 1235325429 My guess is that mail_location is not respected by expire-tool for some reason and in second case mailbox auto-detection makes it working? Thanks, e-frog ---------------------------------------------------------------------------------------------- #: dovecot -n # 1.2.beta1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-11-server i686 Ubuntu 8.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire fts fts_squat mail_plugins(imap): quota imap_quota expire fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: Debian-exim master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 1 expire_dict: proxy::expiredict sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve fts: squat fts_squat: partial=4 full=10 dict: expiredict: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 9

[Dovecot] expire tool - individual user/folder?
by Andre Hübner 02 Jun '09

02 Jun '09

Hello, is the expire plugin usable to delete mails with different settings for each individual user? If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks like expire-data are related to foldernames. Is it possible to let each user "activate" the expire-plugin for different folders with different settings? Thanks, Andre

2 11