- dovecot - dovecot.org

[Dovecot] enabling quota.
by Mauro Sanna 30 Jun '08

30 Jun '08

I'm reading http://wiki.dovecot.org/Quota to enable quota management with dovecot. The first question is: I need to enable dovecot deliver, lda protocol, to have quota work?

2 5

[Dovecot] Global FTS index?
by Patrick Nagel 30 Jun '08

30 Jun '08

Hi, I tried the FTS (and FTS Squat) plugin today, and it works as advertised. But: On my 13000 folders with 160000 mails maildir I use for testing, the speed increase is not as big as one would wish (it still takes several minutes to complete a search). Is my assumption correct, that there is no way to do a search over a big IMAP folder hierarchy in a reasonable amount of time, because each folder has to be 'selected', and only one folder can be selected at once? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

4 5

[Dovecot] Quota Check: fs with multiple "noenforcing" mount point
by Grandy Fu 30 Jun '08

30 Jun '08

Hi, It seems my previous mail has been lost, I apologize if this is a duplicate. I am using Dovecot 1.1.1 with user's INBOX in /var/mail and other folders in their home directories. I have setup file system quota on /var/mail to limit their usage. I would like dovecot to display such information in IMAP client and ignore all others. OS: Solaris 10 Dovecot version : 1.1.1 file system of /var/mail : NFS from Solaris file system of /home : other NFS server that not support rquotad. Here is my setting that works: ---------------------------- plugin { quota = fs:INBOX:mount=/var/mail quota2 = fs:home:noenforcing:mount=/home/h1 } ------------------------------------------ Unfortunately, I have many different mount points for different users, so I changed my settings to: --------------------------- plugin { quota = fs:INBOX:mount=/var/mail quota2 = fs:home:noenforcing:mount=/home/h1 quota3 = fs:home:noenforcing:mount=/home/h2 quota4 = fs:home:noenforcing:mount=/home/h3 } ---------------------------------------------- The result is... Devocolt is not able to get quota information anymore. Any suggestions?

1 0

[Dovecot] quota_warning script
by Nicolas Letellier 29 Jun '08

29 Jun '08

Hello. I'm reading http://wiki.dovecot.org/Quota/1.1 one last time before my upgrade, and I have a question about quota_warning option. Which type of script must we use for this example: quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 What the script must doing? It sends an email? It deletes some emails? Thanks! -- -Nicolas.

2 2

[Dovecot] Dovecot corrupted index cache
by Michael D. Godfrey 28 Jun '08

28 Jun '08

System: Linux 2.6.25.6-55.fc9.x86_64 #1 SMP Tue Jun 10 16:05:21 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux Dovecot: dovecot-1.0.14-8.fc9.x86_64 We have used Dovecot for several years. The error message below appears in the system log quite frequently. I have run a test which shows that this message is due to 2 or more users accessing the same mail (i.e connecting using the same userid). This happens for various reasons including the fact that some users have their client machine set up (typically using Thunderbird) with more than one account within a single Thunderbird configuration. Thus, more than one person may be reading or sending mail from a single Dovecot account. The Dovecot error is: Dovecot disconnects: Inactivity: 13 Time(s) Logged out: 2 Time(s) in IDLE: 12 Time(s) **Unmatched Entries** dovecot: IMAP(godfrey): Connection closed: 4 Time(s) dovecot: IMAP(godfrey): Corrupted index cache file /home/godfrey/Maildir/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(igodfrey): Connection closed: 4 Time(s) =============== or: Dovecot disconnects: Inactivity: 23 Time(s) Logged out: 1 Time(s) in IDLE: 6 Time(s) **Unmatched Entries** dovecot: IMAP(godfrey): Connection closed: 8 Time(s) dovecot: IMAP(godfrey): Corrupted index cache file /home/godfrey/Maildir/.Sent/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(godfrey): Corrupted index cache file /home/godfrey/Maildir/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(igodfrey): Connection closed: 6 Time(s) ---------------------- Dovecot End ------------------------- ========================================================= These errors do not seem to cause any serious problem, but it would be good if the problem could be fixed. I have seen other "corrupted" error reports in the mail archive, but they did not seem to be exactly like this one.

4 5

[Dovecot] Dovecot index, NFS, and multiple architectures
by David Halik 28 Jun '08

28 Jun '08

Hi all, I crawled through the archives for a bit but didn't see anything helpful, so I apologize if this has already been addressed. We've been dying to move from Courier to Dovecot across our whole infrastructure for quite some time, but until recently our setup wasn't possible until this happened: "Dovecot allows mailboxes and their indexes to be modified by multiple computers at the same time, while still performing well. This means that Dovecot works with NFS and clustered filesystems." Now that NFS is officially supported, we figured why not make the switch. All of our mail touches NFS in some way, so we need to check on the stability before completely migrating. In test trials we're having issues with the NFS'd index becoming corrupted. Here's the setup: * Linux workstations running Fedora 8/9 i386 and a locally called Dovecot 1.0.14 * NFS'd homedir with Maildir setup * NFS is on Solaris 9 sparcv9 (64bit) running Dovecot 1.0.14 Now this setup is just a test example and not exactly what we'll be running in production, but it tipped up the problem either way. Since the index is shared by both the Linux i386 machine and the sparc64 Solaris machine, if mail is accessed from both, lets say with Pine for example, the index becomes corrupted and breaks. As long as only one architecture only ever touches it there are no issues. I'm assuming this is an endian issue, which would make the most sense. Is there a way around this with flags or server options? Is this something that has maybe been addressed in 1.1.0? Unfortunately, we are not going to be able to move to Dovecot across all of our systems until this is no longer an issue. We run a lot of mixed environments that have everything from Linux i386/x86_64 to Solaris 9 64 to Windows. If a user accesses IMAP from a Windows box, then logs into the front end which is a Linux x86_64 box and runs Pine, and all of this is on a Solaris sparc NFS system, we're going to have serious issues with the index. ;) Any help would be appreciated. Thanks, -Dave -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu http://www.digitalruin.net ================================

4 9

[Dovecot] Keeping \Seen flag private
by Imobach González Sosa 28 Jun '08

28 Jun '08

Hi all, I wanna to set up shared folders for a couple of users and I'd like that everyone could keep the \Seen flag as private. So if user #1 reads some messages and user #2 not, those messages appear as "unseen" to #2 and "seen" to #1. I've implemented shared folders using namespaces with every user having their own "control" and "private" directories. But all the flags (\Seen included) are "shared". Am I on the right path? Some tip or documentation? Oh, I almost forgot: using dovecot 1.0.13 (from Debian Etch backports). Thank you in advance! -- Imobach González Sosa Banot.net http://www.banot.net/

4 7

[Dovecot] managesieve server aware?
by Cassidy Larson 27 Jun '08

27 Jun '08

Just upgraded to Dovecot 1.1 and thought I'd try out managesieve plugin. My situation is I have two front end proxy boxes and four storage nodes in the back. I have been able to load the managesieve plugin just like I should on the storage nodes, but not on the proxy boxes. My proxy boxes have multiple server sections to deal with unique configurations for 5-7 different mail domains: server mail.host1.com { listen a.b.c.d protocols = imap imaps pop3 pop3s ..... } server mail.host2.com { listen a.b.c.e protocols = imap pop3 .... } If I add the managesieve to the protocols line like I do on my storage nodes, I get this: Error: Can't access mail module directory: /usr/local/lib/dovecot/managesieve: No such file or directory Funny thing is /usr/local/lib/dovecot/managesieve does not exist on the the proxy boxes. It also does not exist on the storage boxes where managesieve loaded just fine. Anybody have any ideas or suggestions? -c

1 1

[Dovecot] Problem Compiling 1.1.1 on AIX
by Jackie Hunt 27 Jun '08

27 Jun '08

Hi all, We've been running Dovecot since December '07 with with no glitches. It's a great solid piece of software, thanks so much Timo!! I thought I'd try out 1.1.1, so I brought it down and tried compiling it on AIX, using the IBM compiler, xlc. It's what I've used all along. The error I'm seeing on the make is: source='array.c' object='array.o' libtool=no DEPDIR=.deps depmode=aix / bin/sh ../../depcomp xlc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/openssl_0. 9.7e/include -g -qcpluscmt -c array.c "macros.h", line 149.68: 1506-211 (S) Parameter list must be empty, or consist o f one or more identifiers separated by commas. make: 1254-004 The error code from the last command is 1. Looking at macros.h, the section it is erroring on is: #ifdef CONTEXT_TYPE_SAFETY # define CONTEXT_CALLBACK(name, callback_type, callback, context, ...) \ ({(void)(1 ? 0 : callback(context)); \ name(__VA_ARGS__, (callback_type *)callback, context); }) #else # define CONTEXT_CALLBACK(name, callback_type, callback, context, ...) \ name(__VA_ARGS__, (callback_type *)callback, context) #endif The second define is the line the error occurs on. Has anyone seen this before. I'm assuming xlc can't handle the '...' parameter, and an hoping there is an option I can enable. Just thought I might see if anyone else has already solved this issue. Thanks much! Jackie ---- Jackie Hunt ACNS Colorado State University Fort Collins, CO 80523

4 5

[Dovecot] (no subject)
by Bruce Bodger 26 Jun '08

26 Jun '08

Timo, Running v1.1.1 on OS X. What is dovecot trying to tell me here? Jun 24 15:03:50 G518X2 dovecot: IMAP(jjohnson): Sort IDs 4 broken in mailbox INBOX, reseting Thank you! G518X2:~ root# dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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 login_process_per_connection: no mail_max_userip_connections(default): 25 mail_max_userip_connections(imap): 25 mail_max_userip_connections(pop3): 10 first_valid_uid: 490 mail_access_groups: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): 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 mail_log_max_lines_per_sec: 0 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/shared:CONTROL=~/Maildir/control/ public:INDEX=~/Maildir/index/public list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you! B. Bodger

3 3