- dovecot - dovecot.org

[Dovecot] Postfix and Dovecot Deliver LDA
by spammy 02 Nov '07

02 Nov '07

Hi all, Having problems moving from postfix/dovecot/mysq/maildrop existing intall to dovecot LDA dovecot -n # 1.0.5: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 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 mail_location: maildir:/vmail/%d/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail master.cf (maildrop line commented. -f ${recipient} in maildrop was working ok) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient} main.cf dovecot_destination_recipient_limit = 1 # I haven't found any docs about the following must work, but apparently working. virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_transport = dovecot dovecot.log dovecot: 2007-11-02 12:32:40 Info: auth(default): master out: USER 1 vaina(a)neenux.com uid=5000 gid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: vaina(a)neenux.com deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: uid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: gid=5000 deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Fatal: setuid(5000) failed: Operation not permitted I'm using vmail:vmail (5000:5000) for all my virtual users and postfix chrooted. I have read the wiki but I'm not using diferrent uids and gids for every user so, I don't understand why deliver is trying to setuid. sorry for my newbie question but my english is not the best and I'm totally lost. any ideas? roger

2 2

[Dovecot] caching custom headers (via plugins)
by Paolo 02 Nov '07

02 Nov '07

hi, currently dovecot caches on disk some most common headers. Is it possible to tweak such headers list via plugins, eg to cache custom X-* headers, or do I need to hack the actual index/cache src? if so, which are the .c/.h files to touch? thanks -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

3 4

[Dovecot] Errors in Dovecot 1.0.5
by Jeff Tucker 02 Nov '07

02 Nov '07

Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) Oct 30 16:11:42 delta2 dovecot: IMAP(x): Raw backtrace: imap [0x462a7e] -> imap [0x46234c] -> imap(mail_index_sync_update_index+0x7b2) [0x44a982] -> imap(mail_index_sync_commit+0xe7) [0x447f87] -> imap(maildir_sync_index_finish+0xd2) [0x420b32] -> imap [0x4225af] -> imap(maildir_storage_sync_init+0x63) [0x4227b3] -> imap(imap_sync_nonselected+0xf) [0x41be9f] -> imap(_cmd_select_full+0xc5) [0x413f95] -> imap(cmd_select+0xb) [0x41411b] -> imap [0x415a87] -> imap [0x415b2c] -> imap(_client_input+0x75) [0x415cd5] -> imap(io_loop_handler_run+0xee) [0x4684ce] -> imap(io_loop_run+0x2d) [0x46797d] -> imap(main+0x3e3) [0x41d7b3] -> /lib/libc.so.6(__libc_start_main+0xdb) [0x2aaaaace049b] -> imap [0x410cca] When this happens, my users just get timeouts trying to do stuff. I have my messages (maildirs) and indices all stored on NFS. For locking, I have mmap_disable = yes and lock_method = dotlock Do you have any idea what is going on here? In general, I get tons of errors about corrupted transaction log files for all users. Is this normal? Thanks Jeff

4 5

[Dovecot] Migration from courier pop3 to dovecot pop3
by Shailesh Singh 02 Nov '07

02 Nov '07

Hello, In mail client users have settings leave message on server. I dont want user download those messages again. i tried with courier-dovecot-migrate.plscript after running this if i am doing send recive all messages downloaded again please help me in this. Thanks Shailesh Singh

2 1

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

02 Nov '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta5.tar.gz.sig APPEND should be working now. Also lots of fixes to handling namespace prefixes and namespaces where virtual separator differs from real separator. zlib plugin now supports opening compressed maildir files. This is done for files that have Z flag. SORT still assert-crashes sometimes. Would be great if someone could show me how to reproduce it. SEARCH TEXT or Squat indexes apparently still have some problems, but I couldn't reproduce them (http://dovecot.org/list/dovecot/2007-October/026254.html)

2 3

[Dovecot] imaptest.c
by sergey ivanov 02 Nov '07

02 Nov '07

Timo, can you, please, update imaptest.c to be compatible with recent 1.1 beta5 dovecot sources? -- WBR, Sergey Ivanov.

2 1

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

02 Nov '07

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft nowadays specifies). + deliver: If message begins with a "From " line, ignore it. + zlib plugin: If maildir file has a "Z" flag, open it with zlib. - CREATE: Don't assert-crash if trying to create namespace prefix. - SEARCH: Fixes to handling NOT operator with sequence ranges. - LDAP reconnection fixes - Maildir: Don't break when renaming mailboxes with '*' or '%' characters and children. - mbox: Fixed "file size unexpectedly shrinked" error in some conditions. - quota+mbox: Don't fail if trying to delete a directory. - Fixes to running from inetd

5 12

[Dovecot] "Can't sync delivery mail"
by Rich Winkel 02 Nov '07

02 Nov '07

Dovecot 1.0.3 Deliver is saying this on two specific emails. Other emails to these 2 users are going through fine. Looking at the mail headers the only thing questionable I see is: From: "AMS Publication Division"@ams.org Is this the problem? # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes shutdown_clients: no login_dir: /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_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 100 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot_indexes/%u lock_method: flock mbox_read_locks: flock mbox_write_locks: flock 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_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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: dovecot

2 4

[Dovecot] Bug within Authentication Caching
by Matthias Waffenschmidt 02 Nov '07

02 Nov '07

Hello, there seems to be a bug in the authentication caching code when using it in combination with username_translation (using the current version 1.0.7 on FreeBSD 6). I've set username_translation to +@:@ to allow usernames of the form test+dom.ain or test:dom.ain (historical reasons force us....). If someone has a successful login using the username test(a)dom.ain, the subsequent authentication information is read from the cache, no matter which of the 3 possible usernames the client uses the next time. But if someone has a successful login using the username test+dom.ain, the following data has or has not been found in the cache: test+dom.ain: miss test(a)dom.ain: miss test:dom.ain: hit If the first username is test:dom.ain the behaviour is the following: test:dom.ain: miss test(a)dom.ain: miss test+dom.ain: hit I've added the information if the username changes for better debugging possibilities. In practice the username is of course always the same. The complete authentication part of the tested config: auth default: cache_size: 10000 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@:+ username_translation: +@:@ verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/pop/%d/Accounts.passwd userdb: driver: static args: uid=70 gid=70 home=/var/emtpy It looks as if Dovecot does some wrong username translations before inserting/lookup up the data in the cache. BTW: a SIGUSR2 signal to the dovecot-auth process does not give any information as suggested in http://wiki.dovecot.org/Authentication/Caching. Please do not only answer to the list as I am not subscribed. Thanks. -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-411 Matthias Waffenschmidt | Ruppmannstr. 27 | fax +49 711 90074-33 mw(a)LF.net | D-70565 Stuttgart | http://www.lf.net

2 1

[Dovecot] Dovecot] Postfix and Dovecot Deliver LDA
by Jerry Yeager 02 Nov '07

02 Nov '07

On Nov 2, 2007, at 9:48 AM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 4 > Date: Fri, 02 Nov 2007 13:00:56 +0100 > From: spammy <spam(a)rogerp.org> > Subject: [Dovecot] Postfix and Dovecot Deliver LDA > To: dovecot(a)dovecot.org > Message-ID: <472B1178.2060200(a)rogerp.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi all, > > Having problems moving from postfix/dovecot/mysq/maildrop existing > intall to dovecot LDA > > dovecot -n > > stuff chomped out > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: > gid=5000 > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Fatal: setuid(5000) > failed: Operation not permitted > > I'm using vmail:vmail (5000:5000) for all my virtual users and postfix (snipped some more out) > > roger Hello Roger, Try this: cd to the path where the dovecot deliver app is. Then, sudo chmod u+s deliver You may or may not need to do sudo chmod g+s deliver -- probably not. This is in the Sendmail - LDA part of the docs. Recent changes to Dovecot seem to have brought this to Postfix - LDA as well. Jerry

1 0