- dovecot - dovecot.org

[Dovecot] logging
by James Devine 19 May '10

19 May '10

I am looking through the logging options and wondering if there are a couple of things that we can do 1. Logouts don't seem to show the IP address of the logout, we typically see multiple sessions at a time and wondering if there is a way to tie the logouts to an IP 2. POP logouts show the number of messages retrieved/deleted but I don't see a way to do this with IMAP, is there a logout option for this with imap? Thanks

1 1

Re: [Dovecot] looking for IMAP testing tool
by Phil Howard 19 May '10

19 May '10

On Wed, May 19, 2010 at 12:49, Mailing List <anonmous(a)dovecot.org> wrote: > Hi Phil, > > I've got an hack piece of regression perl code that we might be a good > starting point. I'd love to turn it into a better piece of hack code > that we could offer up. It does SSL/TLS. > > Right now it is pretty basic and forks 1K-10K simultaneous IMAP > login/logout connections. Its goal is to find the sink point for the > IMAP server and/or test client so that tuning exceeds current usage. > > Let me know if you are interesting in looking at it and cleaning it up. > > ---Jack > The best I could do with something in Perl is rewrite it into something else. I'm still kinda weak on Python (don't know all the cool tricks, yet), and Pike isn't found universally, so things would need to be in C for me to do it and it to be widely usable. And that's for later when I get some free time.

1 0

[Dovecot] looking for IMAP testing tool
by Phil Howard 19 May '10

19 May '10

I'm looking for an IMAP testing tool, suitable to use with Dovecot IMAP. It needs to support TLS, STARTTLS, and login/authentication. It needs to be able run from command line, shell scripts, and even do so under cron jobs (e.g. a way to supply the password to use w/o a terminal prompt). Typical interactive mail clients just don't cut it (even the text mode ones). One reason is I need to do the tests on a number of machines, under a number of user and domain names, and with a variety of parameters or destinations. This is for a suite of regression tests I am putting together intended to verify that configuration changes do not break things (or unbreak things that are supposed to not work). Anyone ever heard of such a tool? Open source would be preferred (better yet, my favorite programming languages: C, Pike, Python).

10 19

[Dovecot] postfix+lda+ virtual users, confusion
by Harry Lachanas 19 May '10

19 May '10

I thought it would be nice to have vboxes insead of user logins ... Now I am confuesed and in trouble .. My server serves 2 domains so user1(a)domain1.com is the same as user1(a)domain2.org I've created the mail_location string with %n and static userdb with %n dovecot creates 2 mail user directories user1(a)domain1.com user1(a)domain2.org What the heck am I missing .. ?? Your help is appreciated Regards Harry Here is my config --------------------------------------------------------------------------------------- base_dir = /var/run/dovecot/ protocols = imap imaps log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_cert_file = /etc/postfix/sasl/cacert.org/mail.pem ssl_key_file = /etc/postfix/sasl/cacert.org/mail.pem ssl_ca_file = /etc/postfix/sasl/cacert.org/cacert.org-root.crt login_greeting = Hi buddy, have an account ?? mail_location = maildir:/home/vmail/%n/Maildir/ namespace private { separator = / prefix = location = maildir:~/Maildir/ inbox = yes } namespace public { prefix = Public/ separator = / location = maildir:/home/Public-Folders-Mail/Public-RO:INDEX=~/Maildir/p1-idx:CONTROL=~/Maildir/p1-ctrl hidden=no subscriptions=no inbox = no list=no } namespace public { prefix = Public-Shared/ separator = / location = maildir:/home/Public-Folders-Mail/Public-RW:INDEX=~/Maildir/p2-idx hidden = no subscriptions = no inbox = no list = no } mail_privileged_group = mail mail_debug = yes verbose_proctitle = yes valid_chroot_dirs = /var/mail:/home/Public-Folders-Mail dbox_rotate_size = 2048 dbox_rotate_min_size = 16 dbox_rotate_days = 0 protocol imap { mail_plugins = zlib autocreate expire imap_client_workarounds = outlook-idle } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = expire } protocol lda { postmaster_address = harry(a)domainxxx.com hostname = mail.domain1.com sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = expire } auth default { mechanisms = plain passdb passwd-file { args = scheme=plain-md5 username_format=%n /usr/local/dovecot/etc/imap.pass3 } userdb static { args = uid=1001 gid=1001 home=/home/vmail/%n } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group= vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { expire = db:/var/lib/dovecot/expire.db } plugin { autocreate = Spam autosubscribe = Spam autocreate1 = Public-Shared/Info autosubscribe1 = Public-Shared/Info autocreate2 = Undetected-Spam autosubscribe2 = Undetected-Spam expire = Trash 2 Trash/* 2 Spam 4 expire_dict = proxy::expire auth_socket_path = /var/run/dovecot/auth-master } -------------------------------------------------------------------------------------

2 1

[Dovecot] mail location filesystem noatime, nodiratime?
by Stan Hoeppner 19 May '10

19 May '10

Will Dovecot be negatively impacted if I change my XFS mount options to noatime,nodiratime? Thanks. -- Stan

4 4

[Dovecot] problem compiling pigeonhole + my fix
by Andreas Schulze 19 May '10

19 May '10

hello, yesterday I tried to package dovecot-2.0beta5 + pigeonhole from Mercurial repository. I put pigeonhole as a subdir in the dovecot sourcetree. Following http://hg.rename-it.nl/dovecot-2.0-pigeonhole/raw-file/tip/INSTALL I called ./autogen.sh; ./configure --with-dovecot=..; make In the buildprocess I saw this output ( from autogen.sh ): Putting files in AC_CONFIG_AUX_DIR, `..'. libtoolize: `config.guess' exists: use `--force' to overwrite libtoolize: `config.sub' exists: use `--force' to overwrite libtoolize: `ltmain.sh' exists: use `--force' to overwrite I dont know *why* AC_CONFIG_AUX_DIR is .. but in .. there are the mentioned files (from dovecot) already present. The following make failed with less helpfull errors. -> my fix is to call "autoreconf -i -f" again after autogen.sh should -f be added to autogen.sh ? -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

2 1

Re: [Dovecot] A new director service in v2.0 for NFS installations
by Timo Sirainen 19 May '10

19 May '10

On 19.5.2010, at 13.09, Cor Bosman wrote: > I guess one of my first questions is, not just how to handle failure of proxies, but also failure of whatever server the proxy sends you to. We've talked about that before, that the proxy could for instance fall back to itself as the 'final server'. The people in here want to use their existing monitoring script that would do "ssh host doveadm director remove 1.2.3.4". But on top of that, yeah, maybe proxy itself could tell director that some host is down and retry the lookup. Although determining when it's down might not be fully reliable always, so I'm a bit worried that proxy could sometimes fail to connect to a mail server even if it's up (but e.g. with high load, temporary small network problem, etc).

1 0

[Dovecot] how to configure my scripts sieves for the home root
by fakessh 19 May '10

19 May '10

hello list hello all reader of this list how to configure my scripts sieves for the home root I encounter these errors in the logs 2010-05-19 14:14:03 deliver(root): Info: sieve runtime error: Not a bytecode file 2010-05-19 14:14:03 deliver(root): Error: sieve_execute_bytecode(/root/.dovecot.sievec) failed thanks for your advice thanks

3 3

[Dovecot] Make dovecot.index and dovecot.index.cache
by Kenji Iuchi 19 May '10

19 May '10

Hi, I would like to make dovecot.index and dovecot.index.cache manually. But that file is made on connecting IMAP Session. That file contribute to performance improvement, so I want to register myself with crontab. Please teach how to make dovecot.index and dovecot.index.cache manyually. Note. Dovecot LDA is not use. -- /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* Kenji Iuchi

2 3

[Dovecot] double write-locking dovecot.index.log
by Mike Abbott 19 May '10

19 May '10

Dovecot's transactions often write-lock dovecot.index.log twice (without unlocking in between), and then unlock it twice. Is that intended, or is that a bug? If I read the man pages correctly, double write-locking is pointless but safe. But double unlocking could cause data corruption during the period between the first and second unlocks, because the locks don't nest (are not refcounted). The first unlock leaves the file totally unlocked. Could this be the source of some index corruption errors? For example: 1. Process A acquires a F_WRLCK on a file. 2. Through a different code path, process A again acquires a F_WRLCK on the same file. Since these locks don't nest this is essentially a no-op. 3. Process A modifies the file. 4. Process A unlocks the file to undo the lock in step 2. Now the file has no lock on it at all. 5a. Process B locks, modifies, and unlocks the file. 5b. Process A also modifies the file, thinking that it still has a write lock. 6. Process A unlocks the file to undo the lock in step 1, but this is another no-op. Data corruption is possible if steps 5a and 5b conflict, or if 5b uses stale data. Here is a code path in dovecot-1.2.11 which exhibits the above behavior. "Outer" write lock: maildir_transaction_save_commit_pre -> maildir_transaction_save_commit_pre_sync -> maildir_sync_index_begin -> mail_index_sync_begin -> mail_index_sync_begin_to -> mail_index_sync_begin_init -> mail_transaction_log_sync_lock -> mail_transaction_log_lock_head -> mail_transaction_log_file_lock -> mail_index_lock_fd -> file_wait_lock -> file_lock_do "Inner" write lock: maildir_transaction_save_commit_pre -> maildir_sync_index_finish -> mail_index_sync_commit -> mail_index_write -> mail_transaction_log_rotate -> mail_transaction_log_file_create -> mail_transaction_log_file_create2 -> mail_transaction_log_file_lock -> mail_index_lock_fd -> file_wait_lock -> file_lock_do The file being locked is the same, dovecot.index.log. In another case, maildir_sync_index_begin is reached this way (outer lock): mailbox_sync -> mailbox_sync_init -> maildir_storage_sync_init -> maildir_sync_context -> maildir_sync_index_begin -> mail_index_sync_begin -> etc. And maildir_sync_index_finish is reached this way (inner lock): mailbox_sync -> mailbox_sync_init -> maildir_storage_sync_init -> maildir_sync_context -> maildir_sync_index_finish -> etc. Could these lead to data corruption? Please let me know if you need any more information. Thanks.

1 1