- dovecot - dovecot.org

New LDA + Sieve (Was Re: [Dovecot] 1.0.rc1 released)
by Timothy White 28 Jun '06

28 Jun '06

> - deliver: Fixed plugin handling settings For sieve support, what is the new procedure? From what I could see, compile WITH deliver support, and then get a plugin from CVS? What has changed in the config files then to enable sieve support? Thanks Tim -- Linux Counter user #273956

3 2

[Dovecot] Colon in maildir folder name breaks keywords
by Bill Boebel 27 Jun '06

27 Jun '06

With maildir, if you have a colon in a folder name, and you try to set a keyword on a message in that folder, the keyword does not get set - and worse, all existing keywords and other status information gets dropped (flagged, seen, replied, trashed). Bill

2 1

[Dovecot] Trash expire plugin
by Timo Sirainen 27 Jun '06

27 Jun '06

Dovecot will soon have a plugin which allows running a nightly cronjob to expunge mails from configured mailboxes which have been in there for a configurable amount of time. For example the configuration could be: plugin { # Trash 7d, Spam 30d expire = Trash 7 Spam 30 } It also supports using Dovecot's lib-dict to keep track of the mailboxes and their oldest mail's timestamp, so that the nightly cronjob can quickly go through only those mailboxes that have those old mails. Berkeley DB support has been added to lib-dict for this purpose, but you could use SQL as well. There's however one problem with it that I could use opinions on. Currently there's no way to know how long a mail has been in a mailbox. There are pretty much 3 ways to handle this: 1) When copying to those Trash/Spam mailboxes the message's INTERNALDATE could be replaced with the current time. That way the INTERNALDATE tells how long the message has been in there. The obvious downside of this is that if the user wants to move the message back to another mailbox, the original INTERNALDATE is lost (INTERNALDATE means the time when the message was received and is often the timestamp used to sort messages). 2) Preserve the INTERNALDATE while copying, but still use it anyway. Often the messages are moved to Trash (and especially to Spam) soon after they have been received. If not, then the user has time until the next nightly cronjob to move the messages back before they're lost. 3) Add a new field to index file which contains the date when the message was copied. This could be done only for those Trash/Spam boxes so they don't waste space for other mailboxes. The problem with this is that it won't work if there are no index files. To overcome that problem the time could be stored in yet another place, such as maildir filename and some new mbox header. I don't see supporting those as worth the trouble though, so the fallback could be either the date index file is created or the messages' INTERNALDATE. I think either 1) or 3) would be best solutions. 3) probably, but if index files don't exist nearly permanently, it's not very reliable..

10 24

[Dovecot] Postfix "userlookup" via Dovecot Auth
by Timothy White 27 Jun '06

27 Jun '06

I'm hoping to take advantage of authentication caching via dovecot-auth. I see that posfix can communicate with Dovecot-Auth, via SASL, but from what I can see, postfix only does this for authentication checks. Not 100% sure how postfix handles virtual_transport (I assume it needs to do a lookup via virtual_mailbox_maps), but I can't see anyway to get virtual_mailbox_maps to use dovecot-auth ether. I guess I may just have to get the virtual_mailbox_maps to look up userdata via SQL as well as Dovecot, but I was hoping to avoid what will be 3 similar lookups one after the other (dovecot-lda is in use as well). My intended setup is "Postfix" -- LMTP --> "Dspam" -- DeliveryAgent --> "Dovecot-LDA", with each stage currently doing a SQL lookup for user information. It would be awesome if they all used SASl via Dovecot-Auth so that the Auth cache does it's job! Reading the doc files in Dspam is confusing me, as the relay file seems to be mixed up. Any help greatly appreciated! Tim -- Linux Counter user #273956

2 1

Re: [Dovecot] maildir quota not including INBOX
by Bill Boebel 27 Jun '06

27 Jun '06

On Tue, June 27, 2006 5:14 pm, Timo Sirainen <tss(a)iki.fi> said: > >Does this still happen? It should return INBOX always, so maybe your >namespace settings somehow causes it to break.. > > >Yes, it is still happenning with last night's CVS. Mail in the INBOX ~/cur and > ~/new directories are not counted during quota recalculations, and also I am seeing > exactly what Steve describes here: > > Fixed now in CVS. Weird that I always had the .INBOX directory created > in all my tests, guess I still run 0.99.x Dovecot once in a while :) > That fixed it. Thanks. Bill

1 0

[Dovecot] Periodic cleanup of Trash
by Anand Buddhdev 27 Jun '06

27 Jun '06

Hi dovecot developers, Is there any plan to have a plugin which deletes old messages from certain folders at login time? I am thinking along the lines of the automatic removal of old messages from say, the Trash folder. This functionality exists in courier-imap and cyrus imap, and would be very handy to have in dovecot too. -- Anand

2 1

Re: [Dovecot] maildir quota not including INBOX
by Bill Boebel 27 Jun '06

27 Jun '06

On Sun, June 11, 2006 1:52 pm, Timo Sirainen <tss(a)iki.fi> said: > On Thu, 2006-04-20 at 20:02 -0400, Bill Boebel wrote: >The maildir quota plugin doesn't appear to be including the INBOX in the quota > calculation that is reported by GETQUOTAROOT. > >I took a look at the code and it appears that in this file > "src/plugins/quota/quota-maildir.c", the function "maildirsize_recalculate" relies > on all of the folders being listed when "maildir_list_init" is called. However the > INBOX is not included in that listing, so its current storage size is not > included. > >I couldn't figure out what patch would be needed to fix this, but I'm sure it is > something simple. Any ideas? > > Does this still happen? It should return INBOX always, so maybe your > namespace settings somehow causes it to break.. > Yes, it is still happenning with last night's CVS. Mail in the INBOX ~/cur and ~/new directories are not counted during quota recalculations, and also I am seeing exactly what Steve describes here: http://www.dovecot.org/list/dovecot/2006-June/014318.html My namespace settings are: namespace private { separator = . prefix = INBOX. inbox = yes location = . } Bill

2 1

[Dovecot] POP3 quota trouble
by Anand Buddhdev 27 Jun '06

27 Jun '06

Hi all, I'm running Dovecot 1.0 beta8 on CentOS 4.3. In the "protocol imap { }" section, I have enabled the following 2 plugins: imap_quota quota In the "plugin { }" section, I have configured the following: quota = maildir imap_quota = maildir This all works well, and if I use IMAP, Dovecot correctly updates the maildirsize file in user Maildirs. However, I need quota to work for POP3 as well. If I enable the quota plugin in the "protocol pop3 { }" section, I get the following error in the log: dlopen(/usr/lib/dovecot/pop3/lib01_quota_plugin.so) failed: /usr/lib/dovecot/pop3/lib01_quota_plugin.so: undefined symbol: mountpoint_get Along with this error, POP3 logins are not possible. The server crashes, and client connection is closed. Is there a fix for this problem? Regards, -- Anand

2 2

Re: [Dovecot] Re: Maildirquota
by Bill Boebel 27 Jun '06

27 Jun '06

On Tue, May 30, 2006 10:02 am, Timo Sirainen <tss(a)iki.fi> said: > On Sun, 2006-05-28 at 20:43 +0800, Timothy White wrote: >userdb static { >args = uid=112 gid=112 home=/var/mail/%1n/%n imap_quota=10485760 >} > > "imap_quota" does nothing. Use "quota" instead. Also its contents should > be something like: > > quota=maildir:storage=10485760 > > If that's correctly configured, then Dovecot creates and updates the > maildirsize file's quota information. Also the GETQUOTAROOT problem Bill > was describing doesn't seem to happen with me if this is correct.. > I am finally getting to test the latest CVS... Yep, our LDAP was returnning a bad quota string. Fixing the quota string corrected the problem I was seeing where calling GETQUOTAROOT would not always recalculate the maildirsize file. Thanks, Bill

1 0

Re: [Dovecot] Problems with dovecot.beta9
by Roy Marples 27 Jun '06

27 Jun '06

> I have been upgraded dovecot today and I get following errors: > >Jun 14 12:08:54 [dovecot] IMAP(adnae at xxxxxx.xxx): inotify_init() failed: >Function not implemented >Jun 14 12:08:54 [dovecot] IMAP(auftrag at xxxxxxx.xxx): inotify_init() >failed: Function not implemented >Jun 14 12:08:54 [dovecot] IMAP(swolf at xxxxxx.xxx): inotify_init() failed: >Function not implemented > >I have a 64 bit system (Gentoo [amd64]) and I have enabled this >function on my kernel: > >Kernel: 2.6.16-gentoo-r9: > [*] Inotify file change notification support One of our developers wanted inotify support in dovecot, and look what happens - lol. The error is that you have glibc-2.4 which triggers inotify support in dovecot on linux boxes (in the Gentoo ebuild). However, glibc-2.4 needs to be compiled against linux-headers-2.6.13 or later as they provide the linux/inotify.h header which glibc needs. I've spoken to our toolchain guys and they don't want to remove glibc's inotify.h so they keep their ABI which makes perfect sense to them. So I've hacked up a patch to dovecots configure.in that only enables inotify if it really works :) It also tests for inotify, then kqueue, then dnotify if no notify method is specified. Seems to work well. If upstream (Timo) accepts it then I'll roll it into beta9's ebuild ASAP A better solution would be to have something in the code though as if the kernel suddenly drops to <2.6.13 then you'll get the same errors. In the meantime, I've forced the beta9 ebuild to only use inotify if >=glibc-2.4 and >=linux-headers-2.6.16 are present, and I hope glibc has been compiled against them - lol. Thanks -- Roy Marples <uberlord(a)gentoo.org> Gentoo/Linux Developer (baselayout, networking)

2 1