May 2010 - dovecot - dovecot.org

[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

[Dovecot] problem trying out dovecot hg
by joakim＠verona.se 18 May '10

18 May '10

I get: May 18 14:56:16 exodia dovecot: master: Dovecot v2.0.beta5 (4ba05c3702be) starting up (core dumps disabled) May 18 14:56:16 exodia dovecot: master: Error: service(pop3-login): safe_mkstemp(/tmp/dovecot-master) failed: Permission denied May 18 14:56:16 exodia dovecot: master: Error: service(imap-login): safe_mkstemp(/tmp/dovecot-master) failed: Permission denied "nc localhost 143" never connects listeners seem to be running at port 143 -- Joakim Verona

3 2

[Dovecot] Shared mailboxes
by spamvoll＠googlemail.com 18 May '10

18 May '10

Hi.. can anyone give me a hind how to setup shared mailboxes. I've already created the shared and private namespace. But ive no idea how to share a mailbox. Thunderbird and most other Clients seem not to support the setacl command. so do i have to create a plaintext file with "user=theldapuseriwanttosharemybox rw" ? thx Hans

5 4

[Dovecot] how authentication works?
by Mihamina Rakotomandimby 18 May '10

18 May '10

Manao ahoana, Hello, Bonjour, I've read: http://wiki.dovecot.org/Authentication/PasswordSchemes I have a users database with clear plain passwords. Dovecot authenticates users without problems against it. Now, it's time to move to CRYPT scheme. Before that, I would like to know how things happen. He have: - the user, (entering his password in the MUA) - the user's MUA (Thunderbird, Outlook, Squirrelmail,...) - the POP or IMAP server - the users database (mySQL) with username and crypt()'d password How I think the process is: - the user enters his password in a clear way. - the MUA sends the password as the user entered it to the POP or IMAP server - the POP or IMAP server fetches the password from the database - the POP or IMAP server crypt()'s the user entered password - the POP or IMAP server compares crypt()'d ones and gives his response Am I close enough to reality? Too far? Misaotra, Thanks, Merci. -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche & Developpement +261 3456 000 19

1 1

[Dovecot] Configuring Dovecot SASL
by BABEDH-DHRA 17 May '10

17 May '10

Dovecot ver = 1.1.11 Dovecot -n = mail:~# dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 6060 mail_privileged_group: mail mail_location: maildir:/var/vmail/%d/%n mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): autocreate quota imap_quota mail_plugins(imap): autocreate quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: mechanisms: plain login cram-md5 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf passdb: driver: sql args: /etc/dovecot/dovecot-crammd5.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir:User quota quota_warning: storage=90%% /usr/sbin/quota-warning.sh 90 quota_warning2: storage=70%% /usr/sbin/quota-warning.sh 70 autocreate: Spam autosubscribe: Spam I am trying to get this to work. I am running a mailserver in Debian Lenny AMD-64 that uses Postfix driven virtual mailbox domains stored in a MySQL database, managed by PostfixAdmin and phpMyAdmin. I must send my mail through DYNDNS through port 2525 the username and password for that service does not appear at all in any of my user names. I have added / merged the data in the Configuring Dovecot SASL but when testing we see nothing about AUTH when testing it. Please let me know if I have left something out I am not a complete NUBE but I am still a bit green. Thanks.

2 1