- dovecot - dovecot.org

[Dovecot] How to startup multi auth daemond
by Xueron Nee 28 Jun '06

28 Jun '06

Hi all， I want restrict some user to use POP3 and some other to use SMTP. I consider to startup multi Auth daemond and each use a diffenent SQL. For example: for pop3： select .... where pop3_service=1 and ... for smtp: select .... where smtp_service=1 and ... I don't know if this is a good idea and how to setup dovecot to do so. Is there any suggest? Thanks! -- Xueron Nee <xueron(a)gmail.com>

2 1

[Dovecot] question indexes recreations
by Konstantin 28 Jun '06

28 Jun '06

Hello! Is it correct not to backup index files in the hope that dovecot will recreate them ?

2 1

[Dovecot] Test
by Tom Alsberg 28 Jun '06

28 Jun '06

Test -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

1 0

[Dovecot] mbox locking
by Thomas Hummel 28 Jun '06

28 Jun '06

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? - when a process abort trying to get a lock after mbox_lock_timeout, does the UA sees anything ? - multiple locking methods in "mbox_write_lock" : if I state, for instance, mbox_write_locks = dotlock fcntl when does exactly dotlock method get used and when does fcntl get used ? Are both used simultaneously ? Which leads to the wiki's deadlock situation example : # Program A: fcntl locks the mbox # Program B at the same time: dotlocks the mbox # Program A continues: tries to dotlock the mbox, but since it's already dotlocked by B, it starts waiting # Program B continues: tries to fcntl lock the, but since it's already fcntl locked by A, it starts waiting why would A dotlock the mbox since he did fcntl'ed it successfully ? if he's able to perform fcntl, he can use a shared or an exclusive lock : why use dotlock at all ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 9

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 28 Jun '06

28 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 28 Jun '06

28 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 28 Jun '06

28 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 28 Jun '06

28 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 28 Jun '06

28 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