- dovecot - dovecot.org

[Dovecot] How to create managesieve core dumps
by Pascal Volk 12 Jul '09

12 Jul '09

I've found this in my dovecot.log: ,--[ /path/to/dovecot.log ]-- | Jul 11 01:44:29 dovecot: Info: Dovecot v1.2.1 starting up | ... | Jul 11 01:50:21 auth(default): Info: client in: AUTH 1 PLAIN service=sieve lip=192.168.111.222 rip=192.168.111.122 lport=12000 rport=35084 resp=<hidden> | Jul 11 01:50:21 auth(default): Info: sql(j.doe(a)example.com,192.168.111.122): query: SELECT "user", password FROM dovecot_password WHERE "user" = 'j.doe(a)example.com' AND sieve | Jul 11 01:50:21 auth(default): Info: client out: OK 1 user=j.doe(a)example.com | Jul 11 01:50:21 auth(default): Info: master in: REQUEST 1 31573 1 | Jul 11 01:50:21 auth(default): Info: sql(j.doe(a)example.com,192.168.111.122): SELECT home, uid, gid, 'dbox:~/dbox' AS mail FROM dovecot_user WHERE userid = 'j.doe(a)example.com' | Jul 11 01:50:21 auth(default): Info: master out: USER 1 j.doe(a)example.com home=/srv/mail/9/70037/70035 uid=70035 gid=70037 mail=dbox:~/dbox ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | Jul 11 01:50:21 managesieve-login: Info: Login: user=<j.doe(a)example.com>, method=PLAIN, rip=192.168.111.122, lip=192.168.111.222 | Jul 11 01:50:21 auth(default): Info: new auth connection: pid=370 | Jul 11 01:51:25 MANAGESIEVE(j.doe(a)example.com): Panic: pool_data_stack_realloc(): stack frame changed | Jul 11 01:51:25 MANAGESIEVE(j.doe(a)example.com): Error: Raw backtrace: managesieve [0x4a45da] -> managesieve [0x4a5360] -> managesieve(i_fatal+0) [0x4a48ce] -> managesieve [0x4b1e6a] -> managesieve [0x4a2421] -> managesieve [0x4a28e9] -> managesieve(buffer_get_space_unsafe+0x2d) [0x4a2d0b] -> managesieve(str_vprintfa+0x6c) [0x4bb149] -> managesieve [0x42a9f7] -> managesieve(sieve_verror+0x100) [0x429c26] -> managesieve [0x44f0a5] -> managesieve [0x44eedf] -> managesieve(sieve_lexer_skip_token+0x15) [0x44f0c8] -> managesieve [0x4322be] -> managesieve [0x4317b2] -> managesieve [0x431ec0] -> managesieve(sieve_parser_run+0x95) [0x432152] -> managesieve(sieve_parse+0x36) [0x42b44b] -> managesieve(sieve_compile_script+0x1d) [0x42b538] -> managesieve [0x4210f5] -> managesieve [0x421678] -> managesieve [0x421474] -> managesieve [0x421787] -> managesieve(cmd_putscript+0x48) [0x4217d1] -> managesieve [0x4231b8] -> managesieve [0x423365] -> managesieve(client_input+0x100) [0x42346f] -> managesieve(io_loop_handler_run+0x17d) [0x4aecfb] | Jul 11 01:51:25 dovecot: Error: child 366 (managesieve) killed with signal 6 (core not dumped - is home dir set?) `-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dovecot v1.2.1/f353c5b71097 was started with: host ~ # ulimit -c unlimited hots ~ # /usr/local/dovecot12/sbin/dovecot ILoading modules from directory: ... IEffective uid=65534, gid=65534, home=/tmp ... ^^^^^^^^^ IEffective uid=65534, gid=65534, home=/tmp ^^^^^^^^^ Why is Dovecot not dumping a core and asking: »is home dir set?«? Regards, Pascal -- The trapper recommends today: cafebabe.0919315(a)localdomain.org

1 1

[Dovecot] Released Sieve v0.1.8 and ManageSieve v0.11.7 for Dovecot v1.2.1
by Stephan Bosch 12 Jul '09

12 Jul '09

Hello Dovecot users, The recent Dovecot v1.2.1 release broke ManageSieve compilation. Today, I release new packages to fix this and additionally a few bugs are resolved. Changelog Sieve v0.1.8: - Fixed AIX compile problem. For portability, the typeof operator is not used anymore. + Added partial support for the deprecated notify extension. However, it turns out that the implementation provided by cmusieve is even older (2001), meaning that this is currently not backwards compatible with cmusieve. Should be fixed in next release. Changelog ManageSieve v0.11.7: * Adjusted to changes in the Dovecot login API. This release now depends on Dovecot v1.2.1 or newer. * Incorporated various small changes in IMAP into ManageSieve. This includes properly enabling the generation of core dumps. - The previous release implicitly resolved the FreeBSD script truncation error. This release adds a small correction to the code that detects the truncation. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed memory leak in the PUTSCRIPT command. (ManageSieve patch) - Forgot to add the managesieve_logout_format setting to the config file. Now it works (bug reported by Pascal Volk). -- The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.8.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.8.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.7.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.7.tar.gz.s… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.1-managesieve-0.11.7.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.1-managesieve-0.11.7.diff.g… -- Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] fchown error on tmp files
by Kim Bisgaard 12 Jul '09

12 Jul '09

Hi, After upgrading to 1.2 I started getting fchown errors in the log. They look like: Jul 12 18:32:54 jukebox dovecot: deliver(kim): fchown(/data/mail/kim/.lists.mythtv-users/tmp/1247416373.M857540P19162.jukebox.alleroedderne.adsl.dk, -1, 500(k im)) failed: Operation not permitted (egid=12(mail), group based on /data/mail/kim/.lists.mythtv-users) I have tried to get rid of the by changing the group of the files to "mail" but that does not help. I can not find a dovecot option that is documented to set the group to %u which would seem ideal. Any advice? Thanks in advance, Kim % dovecot -n # 1.2.0: /etc/dovecot.conf # OS: Linux 2.6.27.25-170.2.72.fc10.i686 i686 Fedora release 10 (Cambridge) ext3 protocols: imaps listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:/data/mail/%u auth default: passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve

2 1

[Dovecot] Dovecot and ACL
by Daniel Spannbauer 11 Jul '09

11 Jul '09

Hello, I try to get per-mailbox-ACLs on dovecot. So, I've modded dovecot.conf: protocol imap { mail_plugins = acl } and plugin { acl = vfile } When I telnet to dovecot an try the command "capability" there is nothing about acl. I need acl for "open-xchange" so I can share Mailboxes over the webinterface. Do I have to create the acl-file manually or does dovecot this automaticly? reagrds Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München

4 11

[Dovecot] imap_quota-error with 1.2.1
by Anton Dollmaier 11 Jul '09

11 Jul '09

Hi, I downloaded the debian-src-package of dovecot 1.2.1 from xi.rename-it.nl, and built the package myself - no errors present. after the upgrade, dovecot complains about an error with imap_quota, startup fails: Restarting IMAP/POP3 mail server: dovecotEdlopen(/usr/lib/dovecot/modules/imap/lib10_quota_plugin.so) failed: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so: undefined symbol: xdr_ext_getquota_args FCouldn't load required plugins Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot/dovecot.conf failed! I downgraded back to 1.2.0, which works normally. Any hints? Best regards, Anton

3 6

[Dovecot] imap connection refused
by Daniel Wallner 11 Jul '09

11 Jul '09

hi, mutt -f imap://max@test.local@127.0.0.1 Could not connect to 127.0.0.1 (Connection refused). lsof -i dovecot 20200 root 5u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20204 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20205 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20206 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) dovecot --version 1.0.15 dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap listen: localhost ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/var/spool/maildirs/%d/%n namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/var/spool/maildir/%d/%n allow_all_users=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: mailsystem group: mailsystem cat /etc/dovecot/dovecot-mysql.conf driver = mysql connect = host=localhost dbname=mailbase user=mailbase password=XXXX default_pass_scheme = PLAIN password_query = SELECT password FROM mailusers WHERE account = '%u' /var/log/dovecot/info.log dovecot: 2009-07-11 09:07:56 Info: Dovecot v1.0.15 starting up dovecot: 2009-07-11 09:07:56 Info: auth-worker(default): mysql: Connected to localhost (mailbase) any ideas why imap is not working? thanks

2 3

[Dovecot] Login Fails: epoll_ctl(1, 7): Operation not permitted
by Thomas Suckow 11 Jul '09

11 Jul '09

Working on setting up dovecot and having trouble logging in. I get an error in logs (below) indicating Operation not Permitted. auth_debug doesn't help. Ideas? # dovecot --version 1.1.7 # dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-gentoo-r5 i686 Gentoo Base System release 1.12.11.1 listen: *,[::] ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/.maildir auth default: verbose: yes debug: yes passdb: driver: pam args: * userdb: driver: passwd Log (server name is adapter, I know it's an odd name...): Jul 9 20:44:48 adapter dovecot: auth(default): new auth connection: pid=11185 Jul 9 20:44:48 adapter dovecot: Fatal: imap-login: io_loop_handle_add: epoll_ctl(1, 7): Operation not permitted Jul 9 20:44:48 adapter dovecot: auth(default): new auth connection: pid=11186 Jul 9 20:44:48 adapter dovecot: auth(default): new auth connection: pid=11187 Jul 9 20:44:48 adapter dovecot: Fatal: imap-login: io_loop_handle_add: epoll_ctl(1, 7): Operation not permitted Jul 9 20:44:48 adapter dovecot: Fatal: imap-login: io_loop_handle_add: epoll_ctl(1, 7): Operation not permitted -- Thomas Suckow

4 7

[Dovecot] problem with convert-tool: "Invalid mailbox name"
by Ezequiel Alfíe 11 Jul '09

11 Jul '09

Hello everyone. I'm having a problem with convert-tool while trying to convert mbox folders to maildir. I'm running dovecot-1.1.16 on Centos 5.3 If the user has subfolders, convert-tool fails saying: "Mailbox conversion: Couldn't create mailbox sub/folder3: Invalid mailbox name" However, if I ran the convert-tool with the same arguments and same folders with dovecot 1.1.11 on Ubuntu 9.04 it works fine. Any pointers for troubleshooting this? Thanks in advance, Ezequiel

2 3

[Dovecot] Relative home directory paths not supported 1.2.1 broke my setup
by Robert Schetterer 10 Jul '09

10 Jul '09

Hi Timo,guess this patch break my setup http://hg.dovecot.org/dovecot-1.2/rev/dd49cf3fd2c9 the log entry does not look very right cause i dont use relative paths or i missinterpreted somthing here Jul 10 21:12:29 dovecot: Error: Relative home directory paths not supported (user robert(a)schetterer.com) maildir:/usr/local/virtual/schetterer.com/robert@schetterer.com/ how can i get my old setup working ? i have user_query = SELECT concat('maildir:/usr/local/virtual/', maildir) AS home, -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] Can expire-tool skip folders with "expire time in future" errors?
by Ralph Seichter 10 Jul '09

10 Jul '09

Hi folks, when I run expire-tool, I often see messages like the following: # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool Info: user/Trash: stop, expire time in future: Fri May 22 17:42:23 2009 the server's dovecot.conf contains the following line: expire = Trash 2 Junk 7 */News 30 */Reports 7 >From what I observe, an error of "expire time in future" in one of the Trash folders stops expire-tool alltogether, meaning that remaining folders like News or Reports don't get processed at all? Is this interpretation correct? If so, can I convince expire-tool to skip errors and continue processing other folders? -R

4 23