- dovecot - dovecot.org

[Dovecot] Maildir Quota and Trash Folder
by Joseph W. Breu 29 Jun '06

29 Jun '06

Is there an option to instruct the imap_quota plugin to count messages in the Trash folder as used space? Thanks, --------------------------------------------------------- Joseph W. Breu, CCNA phone : +1.319.268.5228 Senior Network Administrator fax : +1.319.266.8158 Cedar Falls Utilities cell : +1.319.493.1686 support: +1.319.268.5221 url : http://www.cfu.net

3 3

[Dovecot] [PATCH]: updated tpop3d UIDL support based on older patch
by Arkadiusz Miskiewicz 29 Jun '06

29 Jun '06

Hi, Here is an updated patch which allows to use tpop3d compatible UIDL in dovecot (it's against 1.0rc1): http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/dovecot-tpop3d-uidl.patch?r… which is based on: http://dovecot.org/pipermail/dovecot/2006-March/012080.html Please consider merging it. -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 2

[Dovecot] Running on HPUX
by Rich Rauenzahn 29 Jun '06

29 Jun '06

I've gotten fairly far into compiling and running dovecot on HPUX. The problem I'm currently having is that the index seems to be mmap'ed at twice after login. The 576 byte mmap is the index file: root@hp46t243 # grep mmap64 /tmp/dovecot.tusc [imap ][1707] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][1707] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 8, 0) ........ = 0xc166d000 [imap ][1707] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 9, 0) ........... = 0xc1672000 [imap ][1707] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM [imap ][1717] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][1717] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 9, 0) ........ = 0xc166d000 [imap ][1717] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 8, 0) ........... = 0xc1672000 [imap ][1717] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM [imap ][1897] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][1897] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 9, 0) ........ = 0xc166d000 [imap ][1897] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 8, 0) ........... = 0xc1672000 [imap ][1897] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM [imap ][2042] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][2042] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 9, 0) ........ = 0xc166d000 [imap ][2042] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 8, 0) ........... = 0xc1672000 [imap ][2042] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM [imap ][2178] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][2178] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 9, 0) ........ = 0xc166d000 [imap ][2178] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 8, 0) ........... = 0xc1672000 [imap ][2178] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM [imap ][2318] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xc166c000 [imap ][2318] mmap64(NULL, 18432, PROT_READ, MAP_SHARED, 9, 0) ........ = 0xc166d000 [imap ][2318] mmap64(NULL, 24, PROT_READ, MAP_SHARED, 8, 0) ........... = 0xc1672000 [imap ][2318] mmap64(NULL, 576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) ERR#12 ENOMEM root@hp46t243 # I think multiple mmap's of the same file are verboten -- + In most cases, two separate calls to mmap() cannot map overlapping ranges in a file. The virtual address range reserved for a file range is determined at the time of the initial mapping of the file range into a process address space. The system allocates only the virtual address range necessary to represent the initial mapping. As long as the initial mapping exists, subsequent attempts to map a different file range that includes any portion of the initial range may fail with an ENOMEM error if an extended contiguous address range that preserves the mappings of the initial range cannot be allocated. So, I was trying to look at why the index file is being mapped twice, and why the addr isn't saved and reused. I was thinking of adding it to one of the index structures and skipping the mmap if the addr != 0. I've been poking around for a couple of hours today and am going to call it a day, but I thought I'd ping the list to see if there was something obvious I was missing. Rich

2 4

RE: [Dovecot] APPEND bug in dovecot-20060628
by Bill Boebel 28 Jun '06

28 Jun '06

On Wed, June 28, 2006 1:02 pm, Apps Lists <appslists(a)neonova.net> said: > I'm running maildir quotas with rc1 (dovecot-20060628) and get the > following when trying to APPEND: > "NO Unknown error" > System logs show: > Quota: Couldn't get new message's size > > .... and the file isn't there (unknown if Dovecot removed it, or if the > lack of the file is the cause of the error). I am seeing this problem as well. Running this morning's CVS. Bill

1 0

[Dovecot] APPEND bug in dovecot-20060628
by Apps Lists 28 Jun '06

28 Jun '06

Hi. I'm running maildir quotas with rc1 (dovecot-20060628) and get the following when trying to APPEND: "NO Unknown error" System logs show: Quota: Couldn't get new message's size .... and the file isn't there (unknown if Dovecot removed it, or if the lack of the file is the cause of the error). I reverted back to dovecot-20060621 and APPEND is now working again. Steve

1 0

[Dovecot] quota not working on delivery
by martin f krafft 28 Jun '06

28 Jun '06

Hi, I am using the Debian dovecot packages and the deliver LDA from postfix, all version 1.0.beta8. My problem is with quota support, I am using Maildirs. The relevant configuration stuff is included at the bottom of this email. Quota support seems to work with IMAP. However, even when IMAP complains about an account being over quota, the deliver LDA still happily writes new mail to the (correct) Maildirs. I cannot see any warnings or other hints. Can you spot what I am doing wrong? Thanks! dovecot.conf: protocols = imap default_mail_env = maildir:~/.maildir auth default { mechanisms = plain passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb sql { args = /etc/dovecot/dovecot-sql.conf } socket listen { master { # LDA path = /var/run/dovecot-auth-master mode = 0600 user = vmail } } } plugin { quota = maildir } protocol imap { mail_plugins = quota imap_quota } protocol lda { postmaster_address = postmaster(a)seamus.madduck.net mail_plugins = quota } dovecot-sql.conf: driver = pgsql connect = host=localhost dbname=users user=dovecot password=XXXXXXXX password_query = select password from vmail.users where email='%u' user_query = select home, uid, gid, 'maildir:storage=' || quota as quote from vmail.users where email='%u' -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus(a)madduck.net "women love us for our defects. if we have enough of them, they will forgive us everything, even our gigantic intellects." -- oscar wilde

5 7

[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