June 2008 - dovecot - dovecot.org

[Dovecot] Maildir and Invalid data in file
by Patryk 01 Jul '08

01 Jul '08

Hi Timo, Regarding our conversation in IRC, I'm attaching the uidlist and copying in the original message just in case. I'm using dovecot version 1.0.13 on reiserfs on hardware RAID-0, but I'm getting the following error in the logs every time one user tries to access his old mails in the .Sent directory: dovecot: 2008-06-23 15:09:46 Error: IMAP(marek.chajecki): Invalid data in file /var/mail/Maildir/marek.chajecki/.Sent/dovecot-uidlist As a result he fails to get access to the emails in this folder. I've googled a bit and read that deleting the uidlist makes dovecot recreate it, but after some time the same thing happens. It's a new hard drive, so I don't think this is a hard drive fault. Some additional info: this server is being used by about 200 users who get about 100 emails daily each one of them. Config: root@warsaw Maildir # dovecot -n # 1.0.13: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S ssl_listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_processes_count: 15 login_max_processes_count: 512 max_mail_processes: 4096 mail_privileged_group: mail mail_location: maildir:/var/mail/Maildir/%u maildir_copy_with_hardlinks: yes auth default: worker_max_count: 100 passdb: driver: pam args: cache_key=%u dovecot userdb: driver: passwd Any help will be appreciated! -- Regards, Patryk Rzadzinski

2 1

[Dovecot] Dovecot + Postfix for Squirrel Webmail??
by Marcos Cabrera Goñi 01 Jul '08

01 Jul '08

Hi, I would like to use Dovecot as IMAP Server in order to Develope a Squirrel Webmail. I have a problem with the Dovecot configuration; I have my Postfix server in the host: 192.168.100.100, and I have installed Dovecot in the host: 192.168.1.253. Everything goes right, but I can't see any mail that I had received in my mailbox. How can I configure the dovecot.conf in order to use an mbox placed in a different host?? Thanks. Bye Marcos Cabrera Goñi Departamento de Operaciones Comitas Comunicaciones S.A. Ronda de Poniente 4 Centro Empresarial Euronova 3 28760 - Tres Cantos - Madrid - España Central: +34 91 151 76 00 Móvil: +34 666 578 885 mcabrera(a)comitas.es <mailto:mcabrera@comitas.es>

2 1

[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