- dovecot - dovecot.org

Re: [Dovecot] Dovecot write activity (mostly 1.1.x)
by mikkel＠euro123.dk 05 Nov '07

05 Nov '07

On Sun, November 4, 2007 4:32 pm, Timo Sirainen wrote: >> >> I didn't know that mail_nfs_index=yes resulted in a forced chown. >> How come that's necessary with NFS but not on local disks? >> > > It's used to flush NFS attribute cache. Enabling it allows you to use > multiple servers to access the same maildir at the same time while still > having attribute cache enabled (v1.0 required actime=0). If you don't need > this (and it's better if you don't), then just set the mail_nfs_* to "no" > and it works faster. > >> By the way I misinformed you about fsync_disable=yes. >> It was like that before i upgraded to v1.1, but v1.1 requires >> fsync_disable=no when mail_nfs_index=true so I had to disable it. > > So you use ZFS on the NFS server, but Dovecot is using NFS on client > side? The fsyncs then just mean that the data is sent to NFS server, not a > real fsync on ZFS. > Thanks a lot for the help - this changed a lot! Dist writes fell to about 1/3 of before. I guess the reason is that ZFS can now make use if it's caching capabilities. Delivers activity is completely random since it's impossible to load balance a connection based on the e-mail recipient, since only the ip is known at the load balancing point. Therefore I have fsync_disable=no for deliver. It's easy to force the clients using imap/pop3 to the same server since it can be based on the ip only. Therefore I have fsync_disable=yes for imap/pop3. This changed everything. Now there's a real performance gain upgrading from 1.0.x to 1.1.x. About two or three times less disk activity overall (reads were already improved) for both reads and writes. Thats pretty neat!

1 0

[Dovecot] Version 1.1beta 6 and OS X Leopard (10.5)
by Jerry Yeager 05 Nov '07

05 Nov '07

Just a quick note: The new 1.1-b6 is working fine on OS X 10.5.

1 0

Re: [Dovecot] Testing with some Unstable
by Jeff Grossman 04 Nov '07

04 Nov '07

Andrew Sackville-West wrote: > [SNIPPED] > > actually, assuming you now have unstable in your sources.list, those > are packages currently installed for which there are updates available > (probably unstable updates...). Be careful or you'll end up farther > than you want. > > I can't answer to the specifics of sendmail and libmilter, but so long > as you have unstable in your sources.list, those kept-back packages > will appear (unless you upgrade them, of course). Probably, on the > assumption that sendmail and libmilter is sufficient for your needs, > you should change you sources.list back once those two upgrades are > done. > > A > I have "APT::Default-Release "testing";" in my apt.conf file. Is it still advised to remove the unstable lines from my sources.list file even though I have the above in my apt.conf file? Thanks for you help. Jeff

1 1

[Dovecot] Dovecot write activity (mostly 1.1.x)
by mikkel＠euro123.dk 04 Nov '07

04 Nov '07

Im experiencing write activity thats somewhat different from my previous qmail/courier-imap/Maildir setup. This more outspoken in v.1.1.x than v1.0.x (Im using Maildir). Write activity is about half that of read activity when measuring throughput. But when measuring operations its about 5-7 times as high (measured with zpool iostat on ZFS). I think this might be due to the many small updates to index and cache files. Anyway since writing is much more demanding to the disk than reads dovecots ends up being slower (only a little though) than my old qmail/courier-imap/Maildir was. And the old setup didnt even benefit from indexes like Dovecot does. (What I mean saying slower is that it can service fewer users before it hits the wall). Of course theres also lots of benefits using Dovecot. Im just wondering whether this was a thing that should be focused on for later versions (maybe writes could be grouped together or something like that). Dovecot is very cheap on the CPU side so the only real limit in terms of scalability is the storage. Regards, Mikkel

2 6

[Dovecot] Sieve error messages (sieve 1.1.2, dovecot 1.1b6)
by mikkel＠euro123.dk 04 Nov '07

04 Nov '07

Sorry for spamming the list today:) Im getting a lot of these errors in the deliver log: deliver([recipient]): [date] Info: sieve runtime error: Fileinto: Generic Error deliver([recipient]): [date]:18 Error: sieve_execute_bytecode([path-to-sieve]) failed deliver([recipient]): [date] Info: msgid=<[msgid] >: save failed to [foldername]: Quota exceeded In this case the account is over the defined Dovecot quota limit. Dovecot knows what to do but sieve seems to throw its standard error message. Is there something wrong with Sieve or is it just that the error is misleading? This has been present in all v1.1.x I think (some changes was made to the error messages in b3 or b4 but believe this didnt change). Regards, Mikkel

1 0

[Dovecot] *notify config for 1.0.x doesn't enable inotify
by Paolo 03 Nov '07

03 Nov '07

hi, the current code has changed include linux/inotify.h to sys/inotify.h since 2006-01-17, but that won't work with inotify*.h as documented in the wiki. One has to either revert back to linux/inotify.h, or add #include <sys/inotify-syscalls.h> to both configure.in and src/lib/ioloop-notify-inotify.c Or, just symlink sys/inotify.h -> linux/inotify.h. That's on Debian 3.1 (Sarge). -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

3 6

[Dovecot] IMAP vs system username logging with checkpassword auth
by dale gallagher 03 Nov '07

03 Nov '07

Hi After upgrading to dovecot 1.0.7 I noticed that the actual username is no longer logged, but rather the system user (in my case 'vmail') under which my virtual set-up runs. Now I'm unable to see which virtual users log in. Any pointers on how to configure dovecot to log the actual username given during the IMAP dialogue would be appreciated. My dovecot.conf includes the following: auth default { mechanisms = plain passdb checkpassword { args = /var/qmail/bin/qmail-vauth } userdb prefetch { } user = auth } An example logfile entry: 2007-11-03 15:41:56.027191500 dovecot: Info: imap-login: Login: user=<vmail>, method=PLAIN, rip=192.168.0.141, lip=192.168.0.10, TLS

2 1

[Dovecot] MANAGESIEVE patch v8 for dovecot 1.0.7
by Stephan Bosch 03 Nov '07

03 Nov '07

Hello dovecot users, I have updated the MANAGESIEVE patch to the latest stable version of dovecot (1.0.7). This new version also adds extra configuration settings to explicitly specify the location of the sieve storage and the active sieve script. Additionally, the README now more clearly explains the configuration of the daemon. It currently won't compile with 1.1 due to significant changes in the master code. However, because 1.1 now approaches a stable release, the next version is going to be updated to version 1.1. Change Log V8 ------------- + Fixed a few incompatibilities with 1.0.7 version. For instance, the "Logged in" message is now sent by the -login process and not by the managesieve daemon anymore. This caused a segfault every once in a while. + Probably fixed the settings problem reported by Steffen Kaiser regarding login_dir. 'dovecot -n' now reports correct results, but testing will show whether the whole problem is solved. + The managesieve daemon now accepts the sieve_storage and sieve configuration settings, so it is now possible to explicitly configure the location of the sieve storage and the active script respectively. The daemon still falls back to using the mail_location (MAIL) settings if nothing else is specified. + The cyrus timsieved does not use the + character in string literals and many clients have adopted to this behaviour. The latest managesieve (08) advises to accept a missing + from clients. The server should not send any + characters as well. This behavior is now implemented on the server. + Cleaned up sieve-storage.c: split up the sieve_storage_create function in various sub-functions for obtaining the various paths and directories. + Forced manual intervention if rescueing a non-symlink file at the active script path fails somehow. Previously, this presented the admin with a log message that it had just eaten the script, which is not very nice. + Restructured the README.managesieve file and added some more explanation with regard to the configuration of the daemon. This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.7-MANAGESIEVE-v8.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

4 6

[Dovecot] v1.1.beta6 released
by Timo Sirainen 02 Nov '07

02 Nov '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta6.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta6.tar.gz.sig Fixes since beta5: - dovecot.index.cache file wasn't actually being created/updated (or something like that) - SORT assert-crashed sometimes when sorting by string fields - etc.

1 0

[Dovecot] Listening only on localhost
by tobias-mail＠gmx.net 02 Nov '07

02 Nov '07

Hi! I've got dovecot 1.0.rc15. I want dovecot to listen only on localhost for imap, and on any interfaces for imaps. So I put the following into my config: protocol imap { listen = 127.0.0.1:143 ssl_listen = *:10993 .. } dovecot -n correctly reports: listen: 127.0.0.1:143 ssl_listen: *:10993 But I can still do a 'telnet MY_HOST 143' from the outside, and 'netstat -pltn | grep dovecot' reports: [ip changed ;)] tcp 0 0 77.my.ip.253:10993 0.0.0.0:* LISTEN 4847/dovecot tcp 0 0 77.my.ip.253:143 0.0.0.0:* LISTEN 4847/dovecot Am I doing something wrong? Or is there a bug? -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

3 2